Editing 1495: Hard Reboot

Jump to: navigation, search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 16: Line 16:
 
The correct method of scheduling a regular reboot would be using a ''cron'' task, but perhaps the server is "crashing" in such a dramatic manner that ''cron,'' or ''shutdown,'' or ''init'' stops working. The comic title alludes to this, in that a "hard" reboot scheduled with an analog timer is more guaranteed to work than a "soft" one scheduled with ''cron.''
 
The correct method of scheduling a regular reboot would be using a ''cron'' task, but perhaps the server is "crashing" in such a dramatic manner that ''cron,'' or ''shutdown,'' or ''init'' stops working. The comic title alludes to this, in that a "hard" reboot scheduled with an analog timer is more guaranteed to work than a "soft" one scheduled with ''cron.''
  
If a memory leak is not present, the problem might be fixable by simply increasing swap space; however, if there is a more complex underlying issue, this is the first step along the path of 10 hours of troubleshooting. As a general stereotype, the type of person who has a home server is probably also the kind of person who would start by 'just' increasing the swap size, and before they know it has spent 10 hours completely engrossed in the challenge of fixing the problem. (See [[349: Success]])
+
If a memory leak is not present, the problem might be fixable by simply increasing swap space, however if there is a more complex underlying issue, this is the first step along the path of 10 hours of troubleshooting. As a general stereotype, the type of person who has a home server is probably also the kind of person who would start by 'just' increasing the swap size, and before they know it has spent 10 hours completely engrossed in the challenge of fixing the problem. (See [[349: Success]])
  
 
The subtitle reads "Why everything I have is broken". This indicates that Randall frequently finds himself doing non-standard {{w|Life hacking|workarounds}} that temporarily solve a problem but may ultimately damage the system to the point of becoming nonfunctional. Indeed, a kitchen/light timer used to cut power to a server overnight may affect the server's performance if it is in the middle of a process when the reboot happens. Alternatively, this can be interpreted to mean that everything Randall has is broken and held together by metaphorical duct tape.
 
The subtitle reads "Why everything I have is broken". This indicates that Randall frequently finds himself doing non-standard {{w|Life hacking|workarounds}} that temporarily solve a problem but may ultimately damage the system to the point of becoming nonfunctional. Indeed, a kitchen/light timer used to cut power to a server overnight may affect the server's performance if it is in the middle of a process when the reboot happens. Alternatively, this can be interpreted to mean that everything Randall has is broken and held together by metaphorical duct tape.

Please note that all contributions to explain xkcd may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see explain xkcd:Copyrights for details). Do not submit copyrighted work without permission!

To protect the wiki against automated edit spam, we kindly ask you to solve the following CAPTCHA:

Cancel | Editing help (opens in new window)