General :: Difference Between The Shutdown, Halt And Reboot Commands?
Jan 23, 2011Should I be using one or the other for different things?
View 1 RepliesShould I be using one or the other for different things?
View 1 Repliesdifference between halt, shutdown and poweroff
View 3 Replies View RelatedIs there any way to grant access to non root users to use some commands like reboot and date and some other commands that root user can work with .I tried chmod on their binaries and added them to root group but nothing happened.
View 5 Replies View RelatedFurther to this LQ thread which Tinkster solved by suggesting the last command (thanks Tinkster) I have been exploring last -x reboot and have found that the reported duration is incorrect for the last reboot and shutdown when a old wtmp file is used. Not having a record for the following shutdown, last assumes that the system has been up until the current time and similarly for the shutdown.
The output comes in time order, latest first, each line showing the time of the reboot and the uptime from then to shutdown. Using last -x reboot shutdown to show the shutdown time, here's an illustration
Code:
shutdown system down 2.6.29.6-smp Sun Mar 7 15:35 - 03:02 (11:27)
reboot system boot 2.6.29.6-smp Sun Mar 7 09:35 (05:59)
09:35 until 15:35 is 05:59.
When the uptime exceeds 24 hours it is shown as (<days>+<hours:minutes) like this
Code:
shutdown system down 2.6.29.6-smp Sun Feb 21 12:39 - 13:20 (00:40)
reboot system boot 2.6.29.6-smp Sat Feb 20 09:39 (1+02:59)
09:39 until 12:39 the next day is 1 day 02:59.
The time in parentheses at the end of the shutdown lines is normally the time until the next shutdown.
So far so good. The incorrect output is for the last reboot and shutdown of an old wtmp file. Here's the output of last /var/log/wtmp -x reboot shutdown; last -f /var/log/wtmp.1 -x reboot shutdown
Code:
[snip]
reboot system boot 2.6.29.6-smp Fri Mar 12 07:42 (01:54)
shutdown system down 2.6.29.6-smp Fri Mar 12 01:31 - 09:37 (08:05)
wtmp begins Thu Mar 11 08:25:26 2010
[snip]
reboot system boot 2.6.29.6-smp Wed Mar 10 14:12 (15+01:42)
shutdown system down 2.6.29.6-smp Wed Mar 10 12:41 - 15:54 (15+03:13)
[snip]
The boot started at "Wed Mar 10 14:12" which had an actual uptime of 1 day 11:20 is reported as 15 days 03:13 which is the time from then until the last -f /var/log/wtmp.1 -x reboot shutdown command was issued. The time from shutdown to shutdown is similarly affected.
I'm running V5.3 (newly installed) on an FJ E8020 laptop. The problem I have is when shutting down (*not* rebooting). NetworkManager fails to stop and after (during?) the postfix shutdown, the system seems to hang.I cannot access via another screen or remotely. I can't find any clues in the log files.
[Code]...
I have just started learning linux basic commands.one explain what is the difference between tar and zip commands.
View 7 Replies View RelatedWhat is the difference between the commands tar -xvf and tar -xzf?
View 4 Replies View RelatedDoes the nohup command make a process immune to the HUP signal by sending the process to the background or does it achieve this by some other means? If it it does send it to the background, then are all background processes immune to the HUP signal? If yes, then we can make processes go to the background for getting immunity against HUP by using the bg command as well can't we?
View 2 Replies View Relatedless & more are both the pager commands. Any major difference
View 4 Replies View Relateddifference between these terminal commands?
dpkg -l
dpkg -list
dpkg -list | less
I can't seem to get the options halt and reboot working in my openbox right-click menu. I've tried following the guide here from post #11, where the code he says to use in the /etc/sudoers file is:
%users john=NOPASSWD: /sbin/shutdown -h now, /sbin/shutdown -r now
...but I can't seem to get it to work on my end. In obmenu, I have for halt, to run "sudo halt" and for reboot, "sudo reboot" but they only work after I've already entered my sudo password, such as when I work with terminal to edit a config file.
see if there are differences between init 0 and shutdown -h now?
View 3 Replies View RelatedI haveing a big problem atm (just after to upgrade to 10.04). I have a simply and easy script that sent a halt command to every KVM virtual machine actually running into the server. this script is/and was) palced as a init-rc script in rc0/rc1 and rc6 lvls. Just after to upgrade, I have noticed that this script is executed but the system ignore the time that it require to finish (giving time to correctly stop a single virtual machine). Aftert 5 second it start sending SIG-TERM and SIGN-KILL to any currect process and then reboot/halt.
I have just done a new script using upstart and I got just the same result. What is happending? why is the waiting the init secuence for a valid/or_not termination of any init script. I am so sorry for this crap english I have never study this language so I try to do my best anytime I speak it (or try ti..).
I just started learning network on linux platform. Today I came across two commands ethtool and miitool. Both of them seems to do similar kind of jobs. Now I am confused what is the difference between them.
View 2 Replies View RelatedOnce I halt my desktop machine and then boot it back up, applications previously open will open automatically. Is this some sort of KDE4 feature? Or what process is responsible for this? And is there some sort of file constantly updated about open programs and once I reboot, this file is read by KDE during the boot-up and those previously open programs will be started automatically?
View 2 Replies View Relatedi have a server which was halt on last Thursday(may be halt by some one). using Oracle Enterprise Linux 5.3.
View 2 Replies View RelatedI want to do a shutdown -rF 3:00 to reboot my RHEL server at 3am tomorrow and force an e2fsck on each volume. But I want the e2fsck to run with the -y switch so it automatically answers yes so it will fix any problems it find automatically.
I can't find anywhere where it says if it will do this or not. does anyone know or have proof? Or is there a better way to do what I'm trying to accomplish?
I need to know how to send message (or execute script ) when the linux machine shutdown or reboot stage.
Actually I want to start a backup linux machine when main server shutdown or Reboot.
simply, how we can run script while init 0 OR init 6 command
how to assign shutdown and reboot privileges to the user.please tell directory hierarchy privileges for /root,/bin./lib,/tmp,/var,/pro etc ...
And also i would like to give space quota to particular user and directory for users.
difference between make and make bzImage commands as both are used to build source code.
View 1 Replies View RelatedI'm trying to reboot the server (shutdown -r now).But it seems like nothing happened.
When I try "shutdown -c", the system prompts "shutdown: cannot find pid of running shutdown."
Code:
find . -name *.txt
Code:
find . -name *.txt
I need to clarify a few things about Veritas Cluster Services Example There is a solaris10, 2node vcs cluster running. There is a Rhel5 2node vcs cluster running. Is ther any difference between VCS commands in solaris10 and rhel5. I heard that VCS commands are same for all the platforms, only configuration files location is differ. Is this correct.
View 6 Replies View RelatedI'm currently looking at a Mac Terminal tutorial:[URL]... I want to learn about Linux Terminal, is there a difference between the Mac Terminal and Linux Terminal commands and Internet tutorials?
View 1 Replies View RelatedWhere can I put commands which should be executed just before
- logoff
- shutdown
I think there must be somewhere an opposite script to
.initrc
or
.bashrc
When i tell ubuntu to shutdown it doesn't shutdown but reboots.
View 3 Replies View RelatedI've read through your forums and done a bit of googling to see that an automated reboot at a certain time has something to do with cron jobsMy second task is then to run commands like the following command when the machine starts up again...screen -t s5 ./srcds_run -console -game cstrike -port 27025 +ip xxx.xxx.xxx.xx +map de_dust2 +maxplayers 11 -tickrate 100 -autoupdateit seems to me I need to edit the rd.local but when I open my file I don't really understand where I need to insert my command
View 6 Replies View RelatedI have gotten my touchpad and wireless working after a day of research and help on this forum. The bad news is that I need to enter these commands every time I boot up. I know there is a way to load these commands into the startup. But I am not quite sure where to put them.
# modprobe lib80211
# cd hybrid_wl
# insmod wl.ko
# ifconfig eth1 up
# synclient tapbutton1=1
# synclient tapbutton2=1
# synclient tapbutton3=1
I have recently upgraded to the 10.04 Alpha and have been unable to reboot or shutdown. I know it's just an alpha and therefore problems are bound to exist, so I tried reinstalling from a live cd of Alpha 3. But I am still unable to reboot or shutdown.To clarify what happens, I click on shutdown or reboot, the pop-up appears, I click on the shutdown/reboot button and it seems to complete it. It says that processes have been killed and something has exited with 255. But my computer is still on. I am guessing that Ubuntu is shutting down, it's just not actually shutting my computer down or restarting it.
View 5 Replies View RelatedI have a remote server (Xubuntu 10.04) which suffered an electricity brownout yesterday. The server itself is backed with an ups, but it is connected to a external firewire disk, which is not, and this disk malfunctioned as a result of the brownout.
The problem: Now, any process trying to access the external disk freezes and ends up in eternal D state in the process list, including ls and umount. Even trying to ls a directory which contains a symbolic link to a file in that drive just causes ls to freeze. These processes cannot be killed even with SIGKILL, so I proceeded to reboot but...
None of the reboot commands work. Instead they just get added to the ever increasing list of D state processes. I tried (sudo) shutdown -r now, reboot -f now and finally plain shutdown -h now. Is there anything else to try other than ask somebody to actually go to the server and pull the plug (which is not at all trivial)? Some way to tell kernel not to worry about messing stuff up, and just reboot?