View previous topic :: View next topic |
Author |
Message |
Palironsat n00b
Joined: 19 Feb 2004 Posts: 16 Location: Austin, TX
|
Posted: Sun Nov 26, 2006 8:21 am Post subject: shutdown -h causes reboot... |
|
|
I can't for the life of me figure out why I can't simply shutdown my system. It's probably something stupid that I'm missing, but I just don't know where to start fresh. Can anyone help me out? |
|
Back to top |
|
|
anthrax_ Apprentice
Joined: 17 Oct 2006 Posts: 168 Location: Poland
|
Posted: Sun Nov 26, 2006 8:25 am Post subject: |
|
|
Did you have user added into group wheel? |
|
Back to top |
|
|
Palironsat n00b
Joined: 19 Feb 2004 Posts: 16 Location: Austin, TX
|
Posted: Sun Nov 26, 2006 8:34 am Post subject: |
|
|
Yes. Plus I've done the totally insecure thing and given my standard user account rights to the shutdown command. I'm the only one using this box and it's locked up pretty tight from remote access, so that doesn't bother me.
It doesn't seem to matter, though, whether I'm logged in as user or root, whether I'm shutting down from the console or from E - I get the same results however I try to shutdown. |
|
Back to top |
|
|
madisonicus Veteran
Joined: 20 Sep 2006 Posts: 1130
|
Posted: Sun Nov 26, 2006 7:09 pm Post subject: |
|
|
Check BIOS, maybe? There's often a feature to let you return to previous state after a power outage... could be BIOS misinterpreting a powerdown. Just a passing thought.
GL,
m _________________ Please add [SOLVED] to your message title if you feel that your question has been answered.
------
Intel Q9300 Core2 Quad * Gigabyte GA-EP35C-DS3R
Samsung x360
AMD64 x2 4200+ * TF7050-M2 * HTPC
ZOTAC ION A-U Mini-ITX * HTPC |
|
Back to top |
|
|
SirYes Apprentice
Joined: 15 Jan 2006 Posts: 282 Location: Lodz, Poland
|
Posted: Sun Nov 26, 2006 9:08 pm Post subject: |
|
|
Have you tried "shutdown -P"? (it's supposed to turn off power)
Did it work?
Quote: | could be BIOS misinterpreting a powerdown. |
shutdown writes to the syslog about the method it uses, it's one of the following strings (they can be found in the source code):
- shutting down for system halt
- shutting down for system reboot
So to be completely sure, issue "shutdown -h now" and after reboot check the /var/log/messages (by using "less", for example) and search for last occurrence of "shutting down for system". Then you'll know if the problem lies in software configuration (-h indeed causing reboot) or somewhere else. _________________ My blog: In search for ultimate programming language |
|
Back to top |
|
|
Palironsat n00b
Joined: 19 Feb 2004 Posts: 16 Location: Austin, TX
|
Posted: Mon Nov 27, 2006 4:14 am Post subject: |
|
|
Hadn't even tried shutdown -P. I'll give it a quick shot.
The last few times I've done a shutdown -h, it has given me just a few lines, as follows:
Quote: | Nov 18 01:24:25 localhost shutdown[7036]: shutting down for system halt
Nov 18 01:24:26 localhost init: Switching to runlevel: 0
Nov 18 01:24:30 localhost dhcpcd[5734]: terminating on signal 15
Nov 18 01:24:31 localhost syslog-ng[5312]: syslog-ng version 1.6.9 going down
|
At which point syslog-ng comes back up upon the boot. I'm getting the same result today.
Now, I do have a screwed up bunch of settings for ACPI in the kernel - I could stand to recompile and try again. But, for the time being, the problem still occurs.
I'll come back in a few with an update on shutdown -P. If that does it, I can just create an ACPI event to map that to my power button (which I've already done to -h).
EDIT: No Joy. Shutdown -P causes my system to hard lock. I've got something seriously screwed up here. At this point, I'm going to recompile my kernel with non-screwed ACPI settings and see if that helps. If anybody else has any suggestions, please keep them coming. And thanks to everyone else for their help so far. |
|
Back to top |
|
|
anthrax_ Apprentice
Joined: 17 Oct 2006 Posts: 168 Location: Poland
|
|
Back to top |
|
|
|