On Wed, 24 Jul 2002, Todd A. Jacobs wrote: > On Wed, 24 Jul 2002, Jose Vicente Nunez Zuleta wrote: > > > root 30439 1 0 Jul19 ? 00:00:01 /usr/bin/updatedb -f NFS,SMBFS,N > > root 951 1 0 Jul20 ? 00:00:01 /usr/bin/updatedb -f NFS,SMBFS,N > > root 3886 1 0 Jul21 ? 00:00:01 /usr/bin/updatedb -f NFS,SMBFS,N > > root 13318 1 0 Jul22 ? 00:00:01 /usr/bin/updatedb -f NFS,SMBFS,N > > > > I tried killing them (even with -9) but they are still there :( > > Run pstree or "ps -ax --forest" to see what process owns those updatedb > processes. My guess is it will be cron. You can simply try restarting your > cron daemon if that's the case.
This looks suspiciously like a hung SMB mount (my term). I would bet that the STAT column from "ps -ax" for those processes shows a "D" -- uninterruptible sleep. I have had this happen when my wife's NT machine is turned off before I unmounted the SMBFS mount to it. You can confirm this if "mount" shows an active mount, but a "df" command hangs. (Do this in a shell window you can afford to sacrifice, because it will probably hang the shell permanently like to the updatedb processes.) I don't remember what I did to clear up the condition, but you might try "umount -f" on the bad mount. That may not work, but it's all I can suggest. Jim _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
