Editing Talk:1495: Hard Reboot

My interpretation is that the 1-10 hours is how long it would take to troubleshoot the problem and the 5 minutes is how long it would take to get kitchen timer and put into socket.  So slides are showing the two solutions (one techy and liable to take up to 10 hours vs. the hacky but fast solution). {{unsigned ip|‎108.162.225.118}}

:At first I thought the ten hours was troubleshooting, but 5 minutes sounds about right for the granularity of the timer. [[User:Mikemk|Mikemk]] ([[User talk:Mikemk|talk]]) 06:51, 6 March 2015 (UTC)

''Of course, the problem could be solved without a reboot simply by increasing the swap size.'', my understanding is that the SWAP is overflowing and not just 'too little'. So no, ''simply increasing the swap size'' wouldn't solve the problem. [[Special:Contributions/173.245.53.214|173.245.53.214]] 07:36, 6 March 2015 (UTC)

::I agree, and have removed that sentence, because there is no way to be sure that increasing the swap size will help. In fact increasing the swap size is the first step down the '1-10 hours to troubleshoot' path. --[[User:Pudder|Pudder]] ([[User talk:Pudder|talk]]) 08:52, 6 March 2015 (UTC)
::I think it deserves mention. [[User:Mikemk|Mikemk]] ([[User talk:Mikemk|talk]]) 09:37, 6 March 2015 (UTC)

"Also, it can be scheduled during, say, the middle of the night when most users are sleeping to minimize disruption." That would be ''so'' annoying in my case.  I'm glad Randall has a better discipline of schedule than me, with my Windows NT machine which these days definitely needs its manual weekly reboot and ''really'' needs to be functionally replaced except for all the additional fuss it'd require. (Also, I'm not sure about the "first sentence of the title text" bit, as currently stated, but doubtless it'll all be adjusted slightly.) [[Special:Contributions/141.101.98.181|141.101.98.181]] 12:02, 6 March 2015 (UTC)

:I would recommend 5:00 (am). It's nowhere near the middle of the night, but it's the time when it's most probable everyone is sleeping. Alternatively, considering it's just HIS router, he should know his sleeping patterns ... -- [[User:Hkmaly|Hkmaly]] ([[User talk:Hkmaly|talk]]) 12:11, 6 March 2015 (UTC)

:: When a reboot is least disruptive also depends on whether the machine is being used by users in other time zones. It really annonys me when I'm presented with "Server is down for scheduled maintenance", and the powers that be have decided that the best time to do that is in the middle of the day (for me). --[[User:RenniePet|RenniePet]] ([[User talk:RenniePet|talk]]) 12:42, 6 March 2015 (UTC)

:My reaction to the solution (instead of using cron) was similar to when I see somebody emailing a photo by embedding it in a word document. I guess Randall did that on purpose! [[Special:Contributions/141.101.98.195|141.101.98.195]]

Re: ''"Why everything I have is broken"'' - I think better explanation would be that by applying soem workarounds you can use broken things without actually fixing them. E.g. you can use server with memory leak without spending 10+ hours fixing the problem. Using this approach you can end up with a buch of broken things that are still useful. {{unsigned|Jkotek}}

:This was my understanding of the statement as well. [[Special:Contributions/108.162.216.192|108.162.216.192]] 16:25, 6 March 2015 (UTC)

I think the ''"Why everything I have is broken"'' text refers to the fact that he has spent 10 hours troubleshooting the problem, then implements a hacky fix in 5 minutes which just makes the problem worse - hard rebooting a server every day is not likely to fix the problem and will probably make it worse, and the server will ultimately break. [[Special:Contributions/141.101.99.87|141.101.99.87]] 14:37, 6 March 2015 (UTC)

"The title text's first sentence refers to situations where the given solution to a problem is just the original problem rephrased to sound like a solution." I don't think that's right... it makes it sound like the solution to the problem is to not have the problem, but the first sentence of the title text doesn't reference a solution at all. It's just noting that there's no point in the user looking around for other posts because this is exactly what he's getting, so if there's no solution for this problem then the problem can't be solved. [[Special:Contributions/108.162.219.105|108.162.219.105]] 14:05, 6 March 2015 (UTC)

Thank you for the description! I was reading the 1-10 hours as the time it took for the system to crash, and the 5 minutes as the on-off time -- which obviously conflicted with the 24 hours text in the comic. This makes so much more sense now. =8o) [[User:Jarod997|Jarod997]] ([[User talk:Jarod997|talk]]) 14:42, 6 March 2015 (UTC)
@@ Line 13: / Line 13: @@
 :: When a reboot is least disruptive also depends on whether the machine is being used by users in other time zones. It really annonys me when I'm presented with "Server is down for scheduled maintenance", and the powers that be have decided that the best time to do that is in the middle of the day (for me). --[[User:RenniePet|RenniePet]] ([[User talk:RenniePet|talk]]) 12:42, 6 March 2015 (UTC)
-:::Of course, if you tend to observe a [[28-Hour Day]] it gets tricky to schedule (on a daily basis, at least).  Yes, I used to do somthing like that, a couple of decades ago. (And my mind/body still wants to do it!  Hence why even 5:00am would be awkward for me.  More often than is convenient, anyway.) [[Special:Contributions/141.101.98.188|141.101.98.188]] 11:27, 9 March 2015 (UTC)
 :My reaction to the solution (instead of using cron) was similar to when I see somebody emailing a photo by embedding it in a word document. I guess Randall did that on purpose! [[Special:Contributions/141.101.98.195|141.101.98.195]]
@@ Line 26: / Line 25: @@
 Thank you for the description! I was reading the 1-10 hours as the time it took for the system to crash, and the 5 minutes as the on-off time -- which obviously conflicted with the 24 hours text in the comic. This makes so much more sense now. =8o) [[User:Jarod997|Jarod997]] ([[User talk:Jarod997|talk]]) 14:42, 6 March 2015 (UTC)
-Should one of us ask [[Randall]] if he can tell us which bug this is (assuming it exists), or do the square brackets purposely ask that we should stifle our curiosity? Assuming it's an open-source project, this is an opportunity for readers to make a difference, rather than just humor (cf. [http://forums.xkcd.com/viewtopic.php?f=7&t=71411&sid=b56036e3caa6b410cc34302852c7570f&p=2626767#p2626771|"Randallism"]). [[User:Chrstphrchvz|Chrstphrchvz]] ([[User talk:Chrstphrchvz|talk]]) 22:21, 6 March 2015 (UTC)
-:I don't think it's a specific bug.  It's just humour. [[User:Mikemk|Mikemk]] ([[User talk:Mikemk|talk]]) 01:26, 7 March 2015 (UTC)
-::It might not only be humour. I can say we use the latter technique for a router. [[User:Markhurd|Mark Hurd]] ([[User talk:Markhurd|talk]]) 01:49, 7 March 2015 (UTC)
-::It's xkcd, ''is never just humor''. :P<br>By way, more than hackish, this is just a plain sloppy duck-tape solution.(I mean, at least use a cron job!) [[Special:Contributions/173.245.48.133|173.245.48.133]] 18:31, 7 March 2015 (UTC)
-In the title text, it's THE kitchen timer, not A kitchen timer, so it may mean "the (light) timer from the kitchen"...[[Special:Contributions/188.114.110.47|188.114.110.47]] 12:03, 8 March 2015 (UTC)
-The way the letters are squished together and its general untidiness make the cartoon look rather old. I wondered if it was one Randall dug out that he had drawn a while ago. [[Special:Contributions/108.162.249.182|108.162.249.182]] 22:22, 8 March 2015 (UTC)
-Why is there a description of 3-pronged plugs in the explanation?  It seems to have no context.  [[User:Djbrasier|Djbrasier]] ([[User talk:Djbrasier|talk]]) 13:38, 9 March 2015 (UTC)