Bug#484974: [pkg-ntp-maintainers] Bug#484974: about config files

2012-02-24 Thread Peter Eisentraut
On fre, 2012-02-24 at 01:27 +0100, Pierre Colombier wrote: > Le 23/02/2012 18:33, Peter Eisentraut a écrit : > > Well, everything is moving away from static boot-time-only scripts and > > towards event-based handling (e.g., upstart, udev, dbus), so I think > > that approach is not future-proof. >

Bug#484974: [pkg-ntp-maintainers] Bug#484974: about config files

2012-02-23 Thread Pierre Colombier
Le 23/02/2012 18:33, Peter Eisentraut a écrit : Well, everything is moving away from static boot-time-only scripts and towards event-based handling (e.g., upstart, udev, dbus), so I think that approach is not future-proof. Ok. I respect this point of view. but is there a way to ease / stantard

Bug#484974: [pkg-ntp-maintainers] Bug#484974: about config files

2012-02-23 Thread Peter Eisentraut
On tor, 2012-02-23 at 11:07 +0100, Pierre Colombier wrote: > My main argument about using an init script and not ifup.d is that it > is much more logic and cohérent with how a common administrator > expects to find it. Well, everything is moving away from static boot-time-only scripts and towards

Bug#484974: [pkg-ntp-maintainers] Bug#484974: about config files

2012-02-22 Thread Peter Eisentraut
On sön, 2012-02-19 at 18:07 +0100, Pierre Colombier wrote: > I've made a workaround for me. But altering > /etc/network/if-up.d/ntpdate, can lead to another problem with the > next > update of the package, and i feel uncomfortable with this. > > I think that ndpdate should have his own init scri