On Thu, 08 Apr 2004 22:40:59 +0200, Alexander Dalloz <alexander.dalloz@xxxxxxxxxxxxxxxx> wrote:
Am Do, den 08.04.2004 schrieb Daniel Stonier um 22:31:
Getting updatedb falling into an uninterruptable sleep whenever it tries
to run.
I noticed there's a couple of people who have had the same problem in the
archives, but no solutions to the problem. Has anyone managed to figure out
what's causing it and how to get around it yet?
Cheers, Daniel.
Edit "/etc/cron.daily/slocate.cron" and let the shebang line (first script line) to appear "#!/bin/sh -x" and append to the updatedb line at the end the parameter "-v". Then run "/etc/cron.daily/slocate.cron" by hand and check the output until it 'sleeps'.
Alexander
Actually, not sure its anything to do with updatedb now. Seems my root user
is getting a little unstable. A couple of minutes later I got rpm going
into uninterruptable sleep as well, so I tried an rpm -qa <xxx> with both my
regular user and my root user. Regular user's command worked fine, but the
root one went into uninterruptable sleep.
Rebooted the computer (couldn't think of any other way or reinitialising the
root user) and everything works fine as root again. Be interesting to see
if the problem comes up again.
Thanks for the reply, Daniel Stonier.
-- email:snorri_dj@xxxxxxxxxxxxx http://members.optusnet.com.au/stonierd/
