On Dec 12, 2005, at 1:31 am, Eugene wrote: > On Sat, Dec 10, 2005 at 07:25:26PM CST, Stroller > <macmonster at myrealbox.com> wrote: > : > : On Dec 10, 2005, at 11:25 pm, TjL wrote: > : > > : >disagree all you want, but even finding out a process' path > : >is complicated in Windows Task Manager. And even if you find > : >it and kill it, another process may automatically restart it. > : > : lolol. > : > : And what's to stop another process restarting the one you've just > : killed in OS X? > : Lots of daemons have this behaviour in Unix. > > kill -9 I fail to see how that stops ANOTHER process restarting the one you've just killed. $ cat ./foo.sh #!/bin/bash yes > /dev/null 933 ~ $ ps | grep -e yes -e foo.sh 9991 std R+ 0:00.00 grep -e yes -e foo.sh 934 ~ $ ./foo.sh & [1] 9992 935 ~ $ ps | grep -e yes -e foo.sh 9992 std S 0:00.01 bash ./foo.sh 9993 std R 0:01.64 yes 9995 std S+ 0:00.00 grep -e yes -e foo.sh 936 ~ $ kill -9 9992 9993 [1]+ Killed ./foo.sh 937 ~ $ 937 ~ $ ps | grep -e yes -e foo.sh 9997 std S+ 0:00.00 grep -e yes -e foo.sh 938 ~ $ ./foo.sh & [1] 9998 939 ~ $ ps | grep -e yes -e foo.sh 9998 std S 0:00.01 bash ./foo.sh 9999 std R 0:01.53 yes 10001 std R+ 0:00.00 grep -e yes -e foo.sh 940 ~ $ Obviously you can kill THAT process - the one that's doing the restarting (simulated in this instance by me at the keyboard) - but I don't see why you can't do that in Windows, too. Stroller.