[SOLVED]Shutdown fails, probably because of some config file I changed

Question

Right, i can't shutdown or reboot properly (pm-util's suspend works).
When I try, all (or most, I can't tell) of the deamons are closed properly, but then something attempts to do something with slimlock. It loops so fast I cant' really read the error
message, but I don't think slimlock is even suposed to be accessed at that point.
Deleting slimlock doesn't help, it just gives a "couldn't find command slimlock" (or something similar) error instead.
I have some vague idea that I'm to blame this, because I seem to remember messing around with the shutdown process, trying to get it to call slimlock before anything else.
The thing is; I don't remember.
From now on I'll keep some file with a log of changes I make to scripts and config files, to make this easier, but this time I really need help finding out what the heck I've done : )
Last edited by Bladtman242 (2012-03-10 01:48:46)

Answer 1

I've commented the bash scripts out, and the problem persists.
So I figured I could "limit" the search to
find / -mtime -14 -and -size -2M -exec grep -lisE ".*slimlock.* {} \;"
It turned out to be a "sleep" script in /bin.
I still have no idea why that was called, but I'm marking the thread as solved
Thanks for your efforts
Last edited by Bladtman242 (2012-03-10 01:42:56)