Re: ntpdate from cron -- DON'T DO THAT!
On Sun, Dec 29, 2002 at 02:18:18AM -0800, alan brown wrote:
> I may be wrong but I think it's more generic than burning CD's. I've
> heard it's related to SCSI drives. Just hearsay. Throw it into the
> mix...
On the victim machine I'm using IDE drives with SCSI emulation for the
CD writer, no actual SCSI hardware, and cdrecord to do the writing. In
the course of writing two CDs with about 300 MB the clock slowed by 97
seconds, as subsequently reset by ntpdate. FWIW.
Ken
> -----Original Message-----
> From: Ken Irving
>
> On Sat, Dec 21, 2002 at 04:14:32PM -0800, Bill Moseley wrote:
> > ...
> >
> > The other possibility, brought up by someone on this list, is that > that
> > machine is used for burning CDs and that may cause the clock to get > slow.
> > I have not check this, though.
>
> I'll second that warning, as I saw just that behavior on a time-critical
> system. Yes, it's dumb to be running such processes on a workstation,
> and I'm currently fixing that, but I'm satisfied that burning CDs can
> drastically slow the clock. The last time it happened I easily made the
> connection between the CD burn operation and ntpdate's actions, but the
> first time I had no idea, panicked, and replaced ntpd with ntpdate. > After
> reading this thread I'll go back to ntpd.
>
> --
> Ken Irving <jkirving@mosquitonet.com>
>
>
> --
> To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmaster@lists.debian.org
>
>
>
>
> --
> To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
>
--
Ken Irving <jkirving@mosquitonet.com>
Reply to: