fedora 16 shutdown question

[molossus]

I would like to know if using

shutdown -h now

is ok, i mean for the hard drive , does it force to shutdown too quickly ? does it cause any type of damage when using it instead of Poweroff?

the problem is that when i use the normal "Poweroff" function when pressing ALT in the main menu to shutdown the laptop, it takes too long, about 2 or 3 minutes before it finally shuts down.
but when i use shutdown -h now it shuts down very quickly.

edit: sorry, but both commands take too long to shutdown, i dont know whats wrong with fedora16 RC5.

[Dutchy]

That command doesn't do any harm.
But you probably won't use it any longer because it doesn't give you an advance.
You could look for errors in the system logs what is holding it off.

[lordmarcio]

the command correct is:

shutdown -s now

*-s - shutdown

[DBelton]

-s isn't a valid option for shutdown.

shutdown [OPTIONS...] [TIME] [WALL...]

Shut down the system.

     --help      Show this help
  -H --halt      Halt the machine
  -P --poweroff  Power-off the machine
  -r --reboot    Reboot the machine
  -h             Equivalent to --poweroff, overriden by --halt
  -k             Don't halt/power-off/reboot, just send warnings
     --no-wall   Don't send wall message before halt/power-off/reboot
  -c             Cancel a pending shutdown

[sirio400516x]

How about

 halt -p

Cheers

[lordmarcio]

Ok!
I don't know... I'm sorry

[sirio400516x]

Don't need to be ;-)
Happy shutdown!

[DBelton]

halt -p works

but, you could also just use

poweroff

But, this thread wasn't asking the correct syntax of the shutdown/halt/poweroff commands... It was asking if the shutdown command caused problems due to shutting it down too quickly, and about why F16 was taking so long to shutdown.

There are things that can and will cause delays in shutdown, and sometimes they can be tricky to find since closing the log files are a part of the shutdown procedure. If the hang is after the logs are closed, then you have no means to go back and look to find the cause.

You can boot your system with the kernel options systemd.log_level=debug and systemd.log_target=kmsg and get a little more information if you need to.

You can also save more of the log by dumping it to a different file.

place a shell script in
/lib/systemd/systemd-shutdown:

#!/bin/sh
mount / -orw,remount
dmesg > /dmesg.shutdown
mount / -oro,remount

mark it +x

Then boot with the systemd.log_level=debug and systemd.log_target=kmsg kernel options. You should have your shutdown messages in /dmesg and possibly can see where it is hanging.


Edit:

Just another note on the shutdown -s mentioned above.. It is a valid shutdown option.... IF you were running Windows.

Edit again to correct typo in script above.

[molossus]

Originally Posted by DBelton

halt -p works

but, you could also just use

poweroff

But, this thread wasn't asking the correct syntax of the shutdown/halt/poweroff commands... It was asking if the shutdown command caused problems due to shutting it down too quickly, and about why F16 was taking so long to shutdown.

There are things that can and will cause delays in shutdown, and sometimes they can be tricky to find since closing the log files are a part of the shutdown procedure. If the hang is after the logs are closed, then you have no means to go back and look to find the cause.

You can boot your system with the kernel options systemd.log_level=debug and systemd.log_target=kmsg and get a little more information if you need to.

You can also save more of the log by dumping it to a different file.

place a shell script in
/lib/systemd/systemd-shutdown:

#!/bin/sh
mount / -orw,remount
demsg > /dmesg.shutdown
mount / -oro,remount

mark it +x

Then boot with the systemd.log_level=debug and systemd.log_target=kmsg kernel options. You should have your shutdown messages in /dmesg and possibly can see where it is hanging.


Edit:

Just another note on the shutdown -s mentioned above.. It is a valid shutdown option.... IF you were running Windows.

thank you for that script , , after i did a minor update it shuts down properly and fast

[DBelton]

oops.. I had a typo in that script, too

The command is dmesg, not demsg.