Rich Smrcina wrote:
Cross posted to linux-390 and vse-l, sorry for dups...
http://blogs.computerworld.com/london_stock_exchange_suffers_net_crash
Some (presumed) facts and wild speculation.
I note that three of the Big Four banks host their websites on Windows
boxes. Two run IIS 6, one IIS4!
David Boyes wrote:
I probably shouldn't open this particular can of worms, but... Why
are
you
running ntpdate from cron, anyway?
Because ntpd wakes up periodically to check to see if it needs to do
and crond does not?
--
Cheers
John
-- spambait
[EMAIL PROTECTED] [EMAIL PROTECTED]
-
Cross posted to linux-390 and vse-l, sorry for dups...
http://blogs.computerworld.com/london_stock_exchange_suffers_net_crash
--
Rich Smrcina
VM Assist, Inc.
Phone: 414-491-6001
Ans Service: 360-715-2467
rich.smrcina at vmassist.com
http://www.linkedin.com/in/richsmrcina
Catch the WAVV! http:/
On Tuesday 09 September 2008 12:17, David Boyes wrote:
>> I probably shouldn't open this particular can of worms, but... Why
>>are you running ntpdate from cron, anyway?
>
>Because ntpd wakes up periodically to check to see if it needs to do
>anything, and causes the virtual machine to get dispatc
> I probably shouldn't open this particular can of worms, but... Why
are
> you
> running ntpdate from cron, anyway?
Because ntpd wakes up periodically to check to see if it needs to do
anything, and causes the virtual machine to get dispatched, which causes
CP to have to get it actually ready to
On Monday 08 September 2008 22:53, Martha McConaghy wrote:
>I've been testing out Hobbit in a SLES 10 virtual machine on z/VM. It is
>a monitoring application based off of Big Brother. So far, it works great
>except for one weird thing. We have a cron task that runs once a night
>that does ntpda
Sounds like it is time for some investigation. You didn't give much
information on what exactly is happening. Did you try to kill the process with
"kill -9"? What kernel version are you running? Do you have the latest
patches installed?
I am wondering if the process is catching or ignoring
I'm not familiar with Hobbit, but it sounds a little like some problems
which used to occur with transaction journalling across a time change.
Perhaps changing your ntpdate cron job to do something like this might get
you around the problem:
record the current time, e.g. 00:00:47
stop the Hobbit d
