Hot answers tagged service
Shutdown is preferable because it allows you to specify the reason for the drastic action -- something you should always do. The message will be recorded in the log(s) for posterity. For example: shutdown -r now 'Kernel upgrade requires reboot' You can also perform a scheduled reboot -- by specifying something other than now as the reboot time: shutdown -...
For Red Hat systems, there is no functional difference between reboot and shutdown -r now. Do whatever is easier for you.
If you take a look, in RHEL 7 both /sbin/shutdown and /sbin/reboot are actually just symlinks to systemd's systemctl command. So, use whatever you want. No functional difference as ewwhite told, not even in earlier RHEL releases which did not yet use systemd.
Using reboot is safer. Using reboot your intent is clear and there is no way to mistype it for something else like shutdown -t now which could leads to a few headache if you are using on a remote server with limited control.
According manpage use $SCREEN -ls in order to determine if there already is an active screen in this environment. If there is no logs of your script in /var/log/upstart then try to add debug info in your script
No service is running as PID 4. PID 4 is always the system process itself, in Windows the http.sys kernel driver (running inside of PID 4) usually takes care of all http traffic and services and applications can register IP addresses and URLs to be forwarded to them. Run the following command: netsh http show servicestate or if the output is too long ...
Only top voted, non community-wiki answers of a minimum length are eligible