Cannot reboot Debian Etch - 1 Core at 100% Post: 302360123

3 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Install App in Debian Etch 4.0

I am trying to install a couple applications that I downloaded on my Debian Etch 4.0 OS but I don't know how. 1) I tried using sudo apt-get install...but it always tells me I'm not in the sudoers file 2) I tried using root terminal, but I cant seem to navigate anywhere and I don't know where...

2. Solaris

server reboot itself but no core dump

I wonder if anyone here came accross the same situation like me. One of server in my company reboot itself serveral days ago. I have checked /var/adm/messages... there is nothing there but a few messages mention explorer file has been generated by sysadmin. There is no core dump file either....

3. Debian

Debian Etch - install us-keyboard driver

Hi, i'm using a debian-4.0r1 on an old subnet machine. I have to extend it with an other keyboard . What i have is a DVD of etch 4.0r7. How can i install and load the keyboard-driver for the us-keyboard? Can anybody please give me a hint how to do that? Thanks in advance

LEARN ABOUT POSIX

systemd-halt.service

SYSTEMD-HALT.SERVICE(8) 				       systemd-halt.service					   SYSTEMD-HALT.SERVICE(8)

NAME

       systemd-halt.service, systemd-poweroff.service, systemd-reboot.service, systemd-kexec.service, systemd-shutdown - System shutdown logic

SYNOPSIS

       systemd-halt.service

       systemd-poweroff.service

       systemd-reboot.service

       systemd-kexec.service

       /lib/systemd/systemd-shutdown

       /lib/systemd/system-shutdown/

DESCRIPTION

       systemd-halt.service is a system service that is pulled in by halt.target and is responsible for the actual system halt. Similarly,
       systemd-poweroff.service is pulled in by poweroff.target, systemd-reboot.service by reboot.target and systemd-kexec.service by kexec.target
       to execute the respective actions.

       When these services are run, they ensure that PID 1 is replaced by the /lib/systemd/systemd-shutdown tool which is then responsible for the
       actual shutdown. Before shutting down, this binary will try to unmount all remaining file systems, disable all remaining swap devices,
       detach all remaining storage devices and kill all remaining processes.

       It is necessary to have this code in a separate binary because otherwise rebooting after an upgrade might be broken -- the running PID 1
       could still depend on libraries which are not available any more, thus keeping the file system busy, which then cannot be re-mounted
       read-only.

       Immediately before executing the actual system halt/poweroff/reboot/kexec systemd-shutdown will run all executables in
       /lib/systemd/system-shutdown/ and pass one arguments to them: either "halt", "poweroff", "reboot" or "kexec", depending on the chosen
       action. All executables in this directory are executed in parallel, and execution of the action is not continued before all executables
       finished.

       Note that systemd-halt.service (and the related units) should never be executed directly. Instead, trigger system shutdown with a command
       such as "systemctl halt" or suchlike.

SEE ALSO

       systemd(1), systemctl(1), systemd.special(7), reboot(2), systemd-suspend.service(8)

systemd 237														   SYSTEMD-HALT.SERVICE(8)