On Tue, 2006-02-07 at 11:31 +0000, [EMAIL PROTECTED] wrote: > > > > > > > > I just want to verify if there is anyone here who also suffers this and > > > > what are the proper/needed steps to avoid this? (it's really painful to > > > > have to remember this and do a gradm -D each time) > > > > > > >
Digging deeper, I found that the system would _be_ able to shutdown when it has just been rebooted and a user's cron script has not started executing. When the cron script has been executed, it will refuse to shutdown cleanly and I end up having error messages thrown at me. "/ is busy, unable to unmount" /usr etc...etc.. What does the script do? User = ipaudit Cron = Runs a monitoring script (ipaudit - see freshmeat) for 30 minutes. At each 30 minutes, it will do a "kill -2 script.pid". Upon which it will exit and then process the resulting data. The problem here is that, as "user" he can't view it's own processes. Meaning, with grsec enabled and with PS listing restricted, it will only be able to see the parent process, (which is correct, but killing the parent process will not stop the data collection and continue processing. As a means to sidestep this, I found out that one can actually pass a -2 signal to the process since there's a process id logged. (user can't see this process, but has access to it if he knows the pid) After doing that, then the system refuses to shutdown cleanly. -- Ow Mun Heng Gentoo/Linux on DELL D600 1.4Ghz 1.5GB RAM 98% Microsoft(tm) Free!! Neuromancer 13:48:46 up 1:36, 2 users, load average: 0.64, 1.02, 1.06 -- [email protected] mailing list
