[CLUG] FW: Cork digest, Vol 1 #325 - 4 msgs

[Roycroft, Bryan]

Dermot wrote
Yes, all that. Remember as well thought that the behaviour of the
application can be dependant on how it is programmed to handle
signals. Not all applications are well-behaved. If so programmed a HUP
signal can be treated just like a KILL signal. Bryan, the HUP and KILL
and are just symonmys for the numbers like kill -9 (KILL) that you
find in the signal.h file that comes with your C library.



what I wanted to know was just what the "HUP" option stood for, as I had an
understanding of what kill did, what i've gleaned is that the it is
basically the level which is passed to the command, ie if it should shutdown
or restart. Also in some examples its followed by a file name, it seems to
be the location of the executable that is being restarted. Is this always
necessary or can the OS figure out what to restart from the process context,
as the advice thats in the column just refer to just the process id or is
the HUP the PID and the filename the actual executable to execute, getting
the HUP id.