On Sat, 30 Nov 2002, Jerrad Pierce wrote:
> Because that's not how kill works in UN*X. Kill sends a numbered signal
> (try kill(1) or kill -1). The process then reacts (or not) accordingly.
> End of story. It's not a general purpose interprocess communication
> mechanism. Maybe you want to read perlipc(1).
On the other hand, if it makes any sense [1], you can come up with
wrappers for some of this stuff:
* a config file with different kill settings
* a shell wrapper for the kill command that:
+ updates the config file as necessary
+ sends the kill -HUP signal
* code to read the updated config file when HUP is received
This is very elaborate (and so, prone to error & portability issues), but
if this functionality is critical to you then this would be one way to get
an approximation of it.
[1] Probably, no, it doesn't make all that much sense...
I'm sure there are lots of ways to improve this idea
--
Chris Devers [EMAIL PROTECTED]
_______________________________________________
Boston-pm mailing list
[EMAIL PROTECTED]
http://mail.pm.org/mailman/listinfo/boston-pm
