On Aug 10, 2006, at 1:17 PM, Mike Hunter wrote:
On Aug 10 at 14:22, "Joe Loiacono" wrote:
Having trouble getting flow-capture to stay up. It immediately
dies after
invoking it. I've tested flow-receive and it works fine. Anybody
see the
problem (see below)? I notice that flow-capture will receive a
certain
process ID and then write the next higher one to the PID file. Is
that
standard behavior?
Thanks!
test_pth /flows/pids 125 >ll
total 8
drwxrwxrwx 2 loiacono loiacono 4096 Aug 10 14:15 .
drwxr-xr-x 4 loiacono loiacono 4096 Aug 9 10:41 ..
test_pth /flows/pids 126 >/usr/local/netflow/bin/flow-capture -p
/flows/pids/flowtool.pid -w /flows/nisn_test -E4000M -S3 0/0/2050 &
[1] 1121
test_pth /flows/pids 127 >
[1] Done /usr/local/netflow/bin/flow-
capture
-p /flows/pids/flowtool.pid -w ...
You've double-checked the permissions on nisn_test, I presume? What
happens if you specify the IP addresses explicitly instead of using
"0/0"?
I think it's actually simpler than that. flow-capture daemonizes
itself, by itself.
When you execute it in a shell with a '&', flow-capture is executed
in a background shell. It's the background shell that's returning
immediately.
The sequence is:
1. background shell created with pid 1121
2. background shell starts flow-capture (perhaps with pid 1122, but
this is system dependent)
3. flow-capture daemonizes itself and returns
4. background shell notes that its tasks are complete and exits,
printing [1] Done ...
At this point flow-capture is running on it's own, as a system daemon
(a process unattached to a terminal).
Try it without the "&". The command should return immediately. Use
'ps' to make sure it's running.
-alex
_______________________________________________
Flow-tools mailing list
[EMAIL PROTECTED]
http://mailman.splintered.net/mailman/listinfo/flow-tools
