Re: Re: Keeping a loop alive

Nope, doesn't work. As soon as tcpdump dies, the rest of it closes gracefully. Perhaps I'm overcomplicating matters, but would it help to fork() the process, then monitor the status of the child? Doesn't seem as though that would be theoretically any different than doing the "while (1)" loop.

-fp

Update: Minor correction. If I manually kill tcpdump, the loop does successfully start a new tcpdump process. It's only when I flush the states, and my ssh connection is closed, that it appears to kill off everything. I'm starting to wonder if it isn't a problem with a controlling terminal?

Comment on Re: Re: Keeping a loop alive

Replies are listed 'Best First'.
Re^3: Keeping a loop alive (insufficient spec) by Aristotle (Chancellor) on May 31, 2003 at 16:17 UTC
What is the "the rest of it", and of what is this rest? Makeshifts last the longest.	[reply]
Re: Re^3: Keeping a loop alive (insufficient spec) by fuzzyping (Chaplain) on May 31, 2003 at 16:30 UTC
Actually, it appears to be a controlling terminal problem. If I do `$ ssh user@host 'perl script.pl &'`, then the behavior ceases to be a problem. Sorry for the incorrect analysis. :) -fp	[reply] [d/l]