Hmmm…
“Whatever the cause, the bug disrupted the Saturday evenings of many a system administrator. On the Time-Nuts mailing list, one admin reported spending the evening rebooting hundreds of servers.”
If you ever need to reboot hundreds of GNU/Linux servers, please have sshd running on them and have a list…
for f in able baker charlie delta echo fox;do ssh root@$f "shutdown -r now"&exit
will do the trick. Be sure you have passwordless login as root enabled by distributing the public key for root to all the machines. Your controlling machine will start 2N processes (one on your machine and one on the target) that connect between machines and reboot the targets. After a decent interval you can run another similar script to check that everyone is up again.
for f in able baker charlie delta echo fox;do ping -c 1 $f $2> /dev/null||echo $f unreachable;done What could be simpler? You get the evening off. Isn’t GNU/Linux grand?
I recommend Debian GNU/Linux. It works for you.
Linux is culprit in leap-second lapses: Cassandra exec – PC Advisor.
17494
12777
206
3
2
23944 
11873 
11725 
4643 
4274 
1641 
198 
14 
2 
0 
0 
0 
And you dare speak of “constant re-reboots”…
Phenom wrote, “And you dare speak of “constant re-reboots”…”
No. I write of re-re-reboots… A re-boot once every few years is no problem compared to every few weeks. I once had a machine running XP as a thin client insist on a re-boot in the middle of a class. I migrated it to GNU/Linux with extreme prejudice later in the day.
“A re-boot once every few years is no problem compared to every few weeks.”
Who cares, Pogson. I do know that Google, for example, re-boot their Linux servers every couple of hours on a scheduled sequence, so that only some are rebooting at a time. And I do know this from an engineer at Google. The reason they do it is to eliminate memory leaks, memory fragmentation and resource leaks that certain Java services do.
I’ve also had a system to deal with, where we had the server reboot every midnight due to memory fragmentation stuff of an old Win32-based native application server. Its architecture couldn’t handle well the latest extensions to the systems, combined with the increased scale out of the original specifications.
No one cares about reboots, Pogson. No one, but you and a few others in Loonland.
Phenom wrote, “No one cares about reboots, Pogson. No one, but you and a few others in Loonland.”
There is a huge difference between scheduled reboots and reboots required by a third party. People want IT that works for them.
There are millions of comments on the web about rebooting that other OS. e.g.:
“Windows restarts without warning.
Cause
This issue could be caused by any of the below possibilities.
Software issue or error.
Hardware issue or error.
Heat related issue.
Computer virus.
Issue with operating system.”
Most of those causes are foreign to GNU/Linux users.
Pogson, reboots for Windows updates have been scheduled for the last 8 or so years, I am afraid. Please get an update.
“Hardware issue or error.
Heat related issue”
Now please don’t tell me Linux users are safe from these two.
Phenom wrote, “reboots for Windows updates have been scheduled for the last 8 or so years”.
It was in 2010 that XP told me it was going to reboot in 15 minutes, ready or not. It may have thought I was not using the system because I was logged into my terminal server but that does not excuse interrupting my lecture with a pop-up.
Others have had the same thing happen.