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

Bladtman242 · 2012-03-09 21:50:52

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)

vwyodajl · 2012-03-09 22:24:24

Would searching for modified files over a few days help track what you have been messing with?

find . -mtime +9 -exec ls -lt {} \;

will search for files in the current dir you can change how many days back to search.

Also maybe try reinstalling slimlock? Dont use it so just two guesses
HTH

Bladtman242 · 2012-03-09 23:58:09

Well, I allready tried reinstalling it.
I did a

sudo find /etc -mtime -30 -a -size -2M -exec grep -lisE "slimlock|slim|lock|sleep"

(lock and sleep are bash scripts that both invoke slimlock).
But none of the files seemed to be causing the problem

skunktrader · 2012-03-10 00:05:10

If you were "messing around with the shutdown process" you would probably have edited /etc/rc.local.shutdown or (gulp) /etc/rc.shutdown

Bladtman242 · 2012-03-10 00:57:56

Nope, those files are untouched.
I'm starting to think maybe an update broke this?
It just seems more likely that it would be something I did.
Especially because I do remember looking into making the screen lock on shutdown.

Bladtman242 · 2012-03-10 01:42:31

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)

Bladtman242 · 2012-03-10 01:45:14

Is it possible that I've accidentally overridden the normal sleep command by putting my sleep comand in /bin?

EDIT: God dammit.
That's it. Not only have I overridden it, I've overwritten it. Now the real sleep binary is missing
Any suggestions on how to get it back, and keep it in pacman/yaourt?

EDIT AGAIN: nvm, I explicitly updated coreutils, and that fixed it

Last edited by Bladtman242 (2012-03-10 01:54:50)

Arch Linux

#1 2012-03-09 21:50:52

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

#2 2012-03-09 22:24:24

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

#3 2012-03-09 23:58:09

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

#4 2012-03-10 00:05:10

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

#5 2012-03-10 00:57:56

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

#6 2012-03-10 01:42:31

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

#7 2012-03-10 01:45:14

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

Board footer