Hot answers tagged


For Red Hat systems, there is no functional difference between reboot and shutdown -r now. Do whatever is easier for you.


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 -...


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.


Use: sc.exe config myServiceName obj= "LocalSystem" with sc you can change all kinds of configuration settings for a service. Note the weird syntax with a space after the equal sign.


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 ...


Run mysqld --help and check, if it reports any problems with config Check logs in /var/log/mysql Try runnig it directly and check errors: mkdir /var/run/mysqld/ chown mysql: /var/run/mysqld/ mysqld --basedir=/usr --datadir=/var/lib/mysql --user=mysql --socket=/var/run/mysqld/mysqld.sock


This is due to the switch from init.d to systemd for system services. Check out /etc/init.d/README, which contains a little information about how to live in the new world but doesn't explicitly mention that the service command is now pretty much deprecated.

Only top voted, non community-wiki answers of a minimum length are eligible