By Paul Tero CHAPTER 8bunker where all the servers are kept. You will be thoroughly dependent on
their response time. Given all the risks, the command is:
$ sudo /sbin/reboot
Broadcast message from [email protected] (/dev/pts/1) at 13:21 ...
The system is going down for reboot now.
The reboot command causes the server to shut down and then restart.
That may take a few minutes. Soon after issuing the command above your
SSH session will come to an abrupt end. You will then be left for a few
nervous minutes wondering if it will come back up again. Use the tools
you prepared above.
While you are waiting, you can issue a ping to see if and when your
server comes back. On Windows use ping -t for an indefinite ping:
$ ping http://www.smashingmagazine.com
PING http://www.smashingmagazine.com (80.72.139.101) 56(84) bytes of data.
Request timeout for icmp_seq 0
Request timeout for icmp_seq 0
Request timeout for icmp_seq 0...
64 bytes from http://www.smashingmagazine.com (80.72.139.101): icmp_seq=1 ttl=52
time=39.4 ms
64 bytes from http://www.smashingmagazine.com (80.72.139.101): icmp_seq=1 ttl=52
time=32.4 ms...
You can breathe a sigh of relief when ping finally responds. Wait a
couple more minutes and you’ll be able to use SSH again and then try to
view the Widget 3000 in your Web browser.
Conclusion
This has been an epic journey, from the end of the world to a single
misplaced character in a file. Hopefully, it will help you through the initial
few minutes of panic when you wake up one morning and the beautiful
product page you created last night is gone.