Argus 1.8 Code Freeze Tarfile (fwd)
Peter Van Epp
vanepp at sfu.ca
Thu Sep 16 10:23:07 EDT 1999
> Hey Peter,
> So much for the code freeze %^} You are right, but the topic
> brings up an old dicussion as to what the signals should do.
> Right now we catch them all and exit.
> Chas wanted the ability to get an instantaneous report on
> packets/flows for a ra() that is persistent and writing
> output to a file. This would be a good opportunity to
> define what we want signals to do.
> SIGINT would be a good one for the periodic report, if the
> client supports it. SIGQUIT and SIGKILL seem like they
> should cause the client to exit().
This sounds like a reasonable compromise. You might want to alias
user1 and user2 for the periodic report too (I don't know how you generate
one or if you can from the keyboard). I was looking at the SYSV (Solaris) vs
FreeBSD man pages and signal action is different. It looks like Solaris will
take the default action (which would be exit in this case) but FreeBSD will
return from the signal (which is what it is doing) and I don't see an obvious
way to convince it to exit instead.
Peter Van Epp / Operations and Technical Support
Simon Fraser University, Burnaby, B.C. Canada
More information about the argus