Actually,kill sends a signal to a process. Hup, or 1, usually restarts a process. However, it is up to each program to define how it reacts to any signal.
The two exceptions are the kill signal (9) and the stop signal (26 I think). These signals can not be seen by the program. The OS shuts down or pauses the process. Jim Sent from my iPhone On Nov 24, 2010, at 10:12 AM, Kevin Mattingly <kdmattin...@gmail.com> wrote: > kill is a unix command for stopping a process. The kill -9 is like yanking > the rug out from under something. There is nothing graceful about it. Some > processes should never be stopped using it. If you really need to blow a > process away, you may just be better off to reboot your mac. > > Kev > On Nov 24, 2010, at 12:53 PM, 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 >>>>>> tomacvisionaries+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. -- 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.
