Hi folks,
I've written my program to trap a SIGQUIT and gracefully exit, because
that's what it gets if it's being run in a command prompt and I close
it. It will do the same for a SIGINT (Ctrl+C).
It runs as an HTTP server, so it's supposed to stay up continuously. I
am launching it through an 'at' command in the morning (the server
reboots each night).
For some reason, on some occasions, the program is receiving a SIGQUIT
and shutting down. I know this because it logs that fact. This
happened, for example, last Wednesday and today.
Why would a System process started by the scheduler receive a SIGQUIT?
I don't believe anyone's going in there trying to kill it.
I could solve this problem by making it ignore SIGQUIT, but I wanted it
to behave gracefully when I close a command prompt from which I am
running it. I would rather find out why it is receiving this signal.
Any ideas?
--
Lyle Kopnicky
Software Project Engineer
Veicon Technology, Inc.
_______________________________________________
Perl-Win32-Users mailing list
[email protected]
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
