On Wed, 2011-06-15 at 14:49 +0200, Joachim Backes wrote: > On 06/15/2011 02:39 PM, Patrick O'Callaghan wrote: > > On Wed, 2011-06-15 at 21:55 +0930, Tim wrote: > >> You can log out and find some things still > >> running in your name, that haven't quit, and have no reason to still > >> be > >> around (it's not as if you started up some services that you wanted to > >> run in your name, and stay running after you logged out). > > > > And if you do, that's what nohup is for. > > > >> e.g. Several instances of gvfs-fuse-daemon, crashed mplayers, > >> gconfd-2, > >> firefox (that requires a reboot to kill, not even kill -9 will kill > >> it), > > > > If kill -9 won't kill it, it's suspended in an uninterruptible state in > > the kernel, usually waiting for some "short term" event that will never > > happen. IOW it's a bug. This sort of thing has always existed in Unix > > and related systems and is a PITA, but it's not easy to fix. > > > > poc > > > > But *all* such processes I saw could be killed by "kill" or "kill -9" > (from some tty after having logged out) so why they still exist? Well, if they still exist they clearly weren't killed, and conversely if they were killed then you've been lucky. Note that I'm not addressing your specific problem. My remarks about "kill" were in a general sense about Unix/Linux processes, and unkillable processes do appear from time to time. poc -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
