Bug#392098: [pkg-ntp-maintainers] Bug#392098: ntpdate: init script missing in package
Richard Thrippleton wrote: > As of a recent package upgrade, ntpdate no longer includes the script > in init.d to update the time. That is intentional. Read NEWS.Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#392098: [pkg-ntp-maintainers] Bug#392098: ntpdate: init script missing in package
On Tue Oct 10 14:59, Peter Eisentraut wrote: > Richard Thrippleton wrote: > > As of a recent package upgrade, ntpdate no longer includes the script > > in init.d to update the time. > > That is intentional. Read NEWS.Debian. OK. The implication is that ntp should be the longterm maintainer of time. Is this appropriate for a system with patchy network connectivity that isn't turned on a lot of the time (specifically, my laptop)? I thought the answer to this was "no", so I just had ntpdate run in a cronjob from time to time. What's the correct solution? Richard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#392098: [pkg-ntp-maintainers] Bug#392098: ntpdate: init script missing in package
Richard Thrippleton wrote: > OK. The implication is that ntp should be the longterm maintainer of > time. Is this appropriate for a system with patchy network > connectivity that isn't turned on a lot of the time (specifically, my > laptop)? I thought the answer to this was "no", so I just had ntpdate > run in a cronjob from time to time. What's the correct solution? There are a number of options. You could run ntpd and have ifup/ifdown start and stop it as appropriate. You could run ntpd -q, which does about what ntpdate does. You could run ntpdate when the network is brought up, or from a cron job. Or you use rdate. But none if this requires an ntpdate init script, as far as I can see. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
