Re: tcpdump without Terminal
From: Bruce Barnett (spamhater113+U050127231224_at_grymoire.com)
Date: 01/28/05
- Next message: Nunya Bizness: "Re: unix shell script ignores 'exit' when in function that is piped to tee"
- Previous message: Chris F.A. Johnson: "Re: how to break standard input into 1 character per line"
- In reply to: Gnarlodious: "Re: tcpdump without Terminal"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 28 Jan 2005 04:17:32 GMT
Gnarlodious <gnarlodious@yahoo.com> writes:
> Thanks for the tip, now I am running a file:
>
> sudo nohup tcpdump -i en1 port 80 > /private/tmp/port80.log
>
> Unfortunately the application calling this file now freezes up and needs to
> be forcequit.
I'm not sure which application you are talking about, but did you try
sudo nohup tcpdump -i en1 port 80 > /private/tmp/port80.log &
Some of the versions of tcpdump I have used didn't flush the output
file if I used a "kill ". I have to terminate the tcpdump process with
kill -1 <pid>
to make sure I got the entire packet.
> Is there a way to launch tcpdump without crashing up a process? If so, can
> the tcpdump instance be halted from the shell too?
I have NEVER seen tcpdump crash a process.
Have you used "ps" to find out what was happening?
-- Sending unsolicited commercial e-mail to this account incurs a fee of $500 per message, and acknowledges the legality of this contract.
- Next message: Nunya Bizness: "Re: unix shell script ignores 'exit' when in function that is piped to tee"
- Previous message: Chris F.A. Johnson: "Re: how to break standard input into 1 character per line"
- In reply to: Gnarlodious: "Re: tcpdump without Terminal"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
