[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
user/3746: tcpdump wont write to stdout
- To: gnats@openbsd.org
- Subject: user/3746: tcpdump wont write to stdout
- From: loki@animata.net
- Date: Wed, 14 Apr 2004 10:40:49 +1000 (EST)
- Resent-Date: Tue, 13 Apr 2004 18:55:02 -0600 (MDT)
- Resent-From: gnats@cvs.openbsd.org (GNATS Filer)
- Resent-Message-Id: <200404140055.i3E0t2eU010915@cvs.openbsd.org>
- Resent-Reply-To: gnats@cvs.openbsd.org, loki@animata.net
- Resent-To: bugs@cvs.openbsd.org
>Number: 3746
>Category: user
>Synopsis: "tcpdump -w -" fails
>Confidential: yes
>Severity: non-critical
>Priority: low
>Responsible: bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Wed Apr 14 00:50:01 GMT 2004
>Closed-Date:
>Last-Modified:
>Originator: David Gwynne
>Release: OPENBSD_3_5
>Organization:
net
>Environment:
System : OpenBSD 3.5
Architecture: OpenBSD.i386
Machine : i386
>Description:
Attempting to get tcpdump to write raw dump output to stdout (tcpdump -w -) causes it to fail with the messge "[priv] Invalid state: 2 < 3". This line is generated by the privsep code that is new in this release. Writing to a file (tcpdump -w filename) still works.
>How-To-Repeat:
Simply run /usr/sbin/tcpdump -w -
>Fix:
None at the moment (sorry guys). If I get time at work I'll look further into it.
>Release-Note:
>Audit-Trail:
>Unformatted: