I actually had to reboot a Linux machine tonight to get it to display web pages properly. Restarting apache didn’t do the trick.
Linux reboot
Trackbacks
-
[...] > You sure, ’cause it’s laughably easy to find stories about unscheduled Linux > reboots, ala http://www.mcgees.org/2005/10/13/linux-reboot/ "Linux reboot I actually had to reboot a Linux machine tonight to get it to display web pages properly. Restarting apache didn’t do the trick." LMAO. What a moron. Bother to grok my post, did you, guys? Or is it more fun to point and laugh? I had to reboot the Linux machine to get it to display web pages to the *public* properly, i.e. *serve* web pages properly. Not render them in a browser. SSI was fubared and content was scrambled. An init.d script restart of Apache failed to rectify the situation. Browser caches had nothing to do with it. Of course, I could do what other Linux aficionados do: lie about Linux stability. I’m sure that would get us somewhere. Sincerely, Joshua McGee Linux sysadmin (12 years), Red Hat Certified Technician, and Moron http://www.mcgees.org [...]
-
[...] You sure, ’cause it’s laughably easy to find stories about unscheduled Linux reboots, ala http://www.mcgees.org/2005/10/13/linux-reboot/ I like the t-shirt that says Eat. Sleep. Code., but the others are typical anti-MS goofs by [...]
Subscribe by email
Welcome to the fuckheads who thought I just needed to clear my browser cache. My Linux machine was serving corrupted pages to the public, not displaying old data in a browser cache. An init.d restart of apache failed to fix the problem. Rather than hunt around for the daemon that went haywire, I rebooted (restarted everything) and everything was served properly.
Of course, the modus operandi of Linux users everywhere, whom I have met in the past twelve years of Linux use, is simple: lie and say that Linux never needs rebooting. Me? Not so keen on the self-deception bit.