On Saturday 30 June 2007 20:58, John E. Perry wrote: > Darryl Gregorash wrote: > > On 2007-06-30 19:13, John E. Perry wrote: > >> <snip> > >> > >> (Thanks, Ken, I did know better than to follow Daniel's advice on > >> kill -9, although I have in the past gone straight from kill to > >> kill -9. I'll have to read up on kill to see what -1 is). > > > > 1 is a HUP -- "kill -l" will print a list of all signals. > > Ah. So, using kill -l, I see SIGHUP, SIGINT, SIGQUIT, SIGTRAP, > SIGABRT, and SIGKILL, all of which seem to be closely related. So I > still have some reading to do to understand it and know what to do > (as opposed to following blindly the advice of people who maybe > really know what's going on :-). > > Wait a minute! there's no description of kill with no parameter. and > man, as usual, has no useful information.
Keep in mind that "kill" is one of those commands that exists both as a free-standing binary executable in /bin/kill and as a BASH built-in. As with other commands that live this dual existence, they two are not entirely compatible. Brief information on the BASH built-in is available via "help kill" (only within BASH) or in the man page. /bin/kill -t might help a bit with understanding the different signals, but probably not much. A lot of their meaning and use is somewhat arbitrary and by convention. SIGHUP is generated by tty drivers when the RS-232 DTR signal is deasserted (or the cable disconnected) and by the pseudo-tty driver when no process has master-side open. SIGTERM is used to request a process to shut down gracefully, but immediately. SIGKILL is an unconditional and immediate death, with the target given no attempt to clean up. SIGINT and SIGQUIT are generated by the tty driver when you type (usually) CTRL-C and CTRL-\, resp. And so on. > More googling, I guess. > > jp Randall Schulz -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
