Poor man's unix management
Bart, this is not a poor man's ntp. This is a stupid man's Unix management :)
Do you plan on running that script from cron each day ? Or do you plan on eventually configuring ntp for the boxen ?
Your poor man's configuration management solution would be to use a tool such as dssh or Cluster SSH
However what you really want to do is look into a tool like Puppet and instruct puppet to "Configure NTP on host X-Y-Z"
There's a great article from chromatic about Puppet and Luke over at O'Reilly, you might want to check it out .
Comments
#1 Bart Van Loon : it was just that
hehe, what' all the fuss about? calling people stupid, giving other suggestions which might just be more elaborate, talking about firing people, ... I'm going to have to get the good old tact filter (http://www.mit.edu/~jcb/tact.html) out of the closet again to protect myself against geeks in the wilderness.
it was just that: 6 computers not connected to the Internet (which rules out non-standard tools as suggested by Kris) owned by myself (ruling out firing myself (nobody else *could* do such a thing in the first place)) on which I wished to have the clocks more or less synchronized to do a quick 'n dirty test on.
and it worked. :-)
#2 Ghosty : Security
And then he did not even talk about security, allowing root login on all your boxes? talk about a hole!
I just started puppet and am starting to be a big fan of it ...
#3 Kris Buytaert : I didn't dare to
add yet another topic .. obviously I'd fire people fore allowing remote root but then again ..
We have to teach people step by step ..
And make sure Serge still allows us to come to geekdinners :)
#4 Serge van Ginderachter : Stupid?
When calling somebody stupid, you might at least elaborate your motivation ;-)
#5 Kris Buytaert : I did :)
I asked if he planned on running that script from cron, over and over , and over again ..
He didn't solve the problem, he solved a sympton, not that smart heh :)
Then I went on to explain what he could have done to solve the problem :)