Oh the kill command is a throwback to the unix underpinnings of the mac. On unix devices you use the kill command to restart or kill a prcess. Processes have id numbers and process names which can be used to identify the process you want to restart or kill.
Something like kill -1 1 reruns the init process and restarts something like kill -HUP 914 will kill process tagged with the ID 914 and restart similar to a reload a kill -9 2332 will kill and not restart the process tagged with 2332 and also will not allow 2332 to gracefull shutdown. It's all about process control. there is also pkill in some systems where you can do pkill -hup named and restart the process called named or bind in this case. pkill -HUP inetd will restart the inetd process etc. Hope that clears it up a little. On Nov 24, 2010, at 9:53 AM, Carolyn wrote: > Ah, leave it to Scott to bring us some grace.:) I haven't a clue what y'all > are talking about. But I guess I should know this in case Alex ever decides > to give me the silent treatment. I don't recall an initial post on this but > better save these in a backup for future reference. > To all who care: Happy Thanksgiving > > Carolyn > ----- Original Message ----- > From: Scott Granados > To: macvisionaries@googlegroups.com > Sent: Wednesday, November 24, 2010 10:36 AM > Subject: Re: The KillAll command > > Whoa -9 and -hup do * not * do the same thing. > > > -9 is a kill all with no graceful shutdown. -HUP is a restart, -1 is a > graceful shutdown. > > > On Nov 24, 2010, at 8:41 AM, Geoff Waaler wrote: > >> Hi Eric and Nic, >> >> Thanks much -- the -9 seems to cause a restart, hence appears to have the >> identical affect of the -hup parm. >> >> On Nov 24, 2010, at 3:22 AM, Nicolai Svendsen wrote: >> >>> Hi! >>> >>> True enough. -HUP accomplishes the same thing, though, but of course the >>> parameters mean something different. I always just use -9 to ensure it >>> actually quits, and it's just as efficient in the long-run. And, it's less >>> parameters to type. >>> >>> Regards, >>> ic >>> GoogleTalk: chojiro1...@gmail.com >>> Facebook >>> Twitter >>> Skype: Kvalme >>> MSN Messenger: nico...@home3.gvdnet.dk >>> Yahoo! Messenger: cin368 >>> AIM: cincinster >>> >>> On Nov 24, 2010, at 10:08 AM, Eric Oyen wrote: >>> >>>> the killall command works. -9 will simply force it to quit. I prefer the >>>> use of killall -HUP VoiceOver as it forces a reset of voiceover without >>>> going through all the issues of restarting it via keystrokes. btw, you >>>> must capitalize the V and the O otherwise it will not find the process >>>> name. >>>> >>>> -Eric >>>> >>>> On Nov 24, 2010, at 1:53 AM, Geoff Waaler wrote: >>>> >>>>> Greetings, >>>>> I meant to reply to one of Nic's recent posts, but deleted it. He >>>>> suggested that if VO goes silent one could enter terminal into spotlight >>>>> and then enter -- I forget the exact command but believe it was >>>>> killallall -9 voiceover. >>>>> >>>>> I tried this with and without the extra "all" and also tried inserting a >>>>> space between the two alls, but only receive a message that no matching >>>>> processes were found. >>>>> >>>>> I'd like to get this right in case I do experience a vo crash. May not >>>>> have recalled the parm Nic mentioned, but I did use the one he specified >>>>> (which may not have been -9). >>>>> >>>>> TIA for any clarification, and best regards. >>>>> Geoff >>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google Groups >>>>> "MacVisionaries" group. >>>>> To post to this group, send email to macvisionar...@googlegroups.com. >>>>> To unsubscribe from this group, send email to >>>>> macvisionaries+unsubscr...@googlegroups.com. >>>>> For more options, visit this group at >>>>> http://groups.google.com/group/macvisionaries?hl=en. >>>>> >>>> >>>> -- >>>> You received this message because you are subscribed to the Google Groups >>>> "MacVisionaries" group. >>>> To post to this group, send email to macvisionar...@googlegroups.com. >>>> To unsubscribe from this group, send email to >>>> macvisionaries+unsubscr...@googlegroups.com. >>>> For more options, visit this group at >>>> http://groups.google.com/group/macvisionaries?hl=en. >>>> >>> >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "MacVisionaries" group. >> To post to this group, send email to macvisionar...@googlegroups.com. >> To unsubscribe from this group, send email to >> macvisionaries+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/macvisionaries?hl=en. > > > -- > You received this message because you are subscribed to the Google Groups > "MacVisionaries" group. > To post to this group, send email to macvisionar...@googlegroups.com. > To unsubscribe from this group, send email to > macvisionaries+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/macvisionaries?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "MacVisionaries" group. > To post to this group, send email to macvisionar...@googlegroups.com. > To unsubscribe from this group, send email to > macvisionaries+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/macvisionaries?hl=en. -- You received this message because you are subscribed to the Google Groups "MacVisionaries" group. To post to this group, send email to macvisionar...@googlegroups.com. To unsubscribe from this group, send email to macvisionaries+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/macvisionaries?hl=en.
