Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
localhost kernel:kernel log daemon terminating.
localhost syslog:klogd shutdown succeeded
localhost exiting on signal 15
localhost syslogd 1.4.1:restart
You are right. I will be more specific. I want the system to poweroff. what should i do in this case? One of my friend when uses init 0, system will shutdown and power gets off.
Also, i used "shutdown -a now", but no use
/sbin/shutdown [-t sec] [-arkhncfFHP] time [warning-message]
shutdown brings the system down in a secure way. All logged-in users are notified that the sys-
tem is going down, and login(1) is blocked. It is possible to shut the system down immediately
or after a specified delay. All processes are first notified that the system is going down by
the signal SIGTERM. This gives programs like vi(1) the time to save the file being edited, mail
and news processing programs a chance to exit cleanly, etc. shutdown does its job by signalling
the init process, asking it to change the runlevel. Runlevel 0 is used to halt the system, run-
level 6 is used to reboot the system, and runlevel 1 is used to put to system into a state where
administrative tasks can be performed; this is the default if neither the -h or -r flag is given
to shutdown. To see which actions are taken on halt or reboot see the appropriate entries for
these runlevels in the file /etc/inittab.
-a Use /etc/shutdown.allow.
-t sec Tell init(8) to wait sec seconds between sending processes the warning and the kill sig-
nal, before changing to another runlevel.
-k Don't really shutdown; only send the warning messages to everybody.
Distribution: Red Hat Enterprise Linux / Fedora 11
I found this on another forum, perhaps this would help?:
Give apm a shot. When you boot, go into the grub menu and press "e" to edit the ubuntu selection. Edit the kernel like by pressing "e" again. Go to the end of the line and add "apm=force" and hit enter. Then press "b" to boot.
If that fixes it, add "apm=force" to the line in /boot/grub/menu.list
## nonaltoption boot targets option
## This option controls options to pass to only the
## primary kernel menu item.
## You can have ONLY one nonaltoptions line
# nonaltoptions=quiet splash apm=force
You can also see what your bios is set to (apm or acpi)