Re: Effectiveness of ntp under Redhat Linux FC3
From: Nico Kadel-Garcia (nkadel_at_comcast.net)
Date: Sun, 22 May 2005 08:55:05 -0400
"Roy Culley" <firstname.lastname@example.org> wrote in message
> "Nico Kadel-Garcia" <email@example.com> writes:
>> May I be wildly amused at sending a *.vbs attachemt to a Linux
> There was no virus attached to my post. Perhaps there is something
> wrong with your newsreader?
I didn't say it was a virus. Hmm. I'm using Outlook Express for ease of
reading and attachment access. (I'm on my home box,which is a Windows box so
my daughter can use it for games, and your message I commented on shows this
in the raw source: The "begin risky.vbs" at the start of the message is
causing it to show up now as an attachment, not as content, which is why I
Michael Ward <firstname.lastname@example.org> writes:
> Hello All,
> I've configured my FC3 system to run ntp successfully at boot time and
> ntp seems to run successfully for about a day. However, every night
> clock looses some 1200 seconds while the system is busy making
> When ntp figures this out, it refuses to update the clock because
> is classified as insane, and terminates.
ntp should be running at a high priority. If not then it isn't being
started correctly. When running at high priority your backup shouldn't
affect it assuming the backup is running at a higher priority.
Hmm. It's not my newsreader adding it, you seem to use "begin risky.vbs"as
your reply header. Can I ask you not to use that as your reply header? It
causes confusion and causes your content to show up as a *.vbs attachment,
and forces various readers to attempt to deal with your text as an
attachment, which it is not (which I see upon examination).