[pkg-ntp-maintainers] Bug#478655: Bug#478655: ntp: other solution

Vladimir Stavrinov vs at inist.ru
Thu May 1 14:52:00 UTC 2008


On Thu, May 01, 2008 at 02:47:45PM +0200, Kurt Roeckx wrote:

> It's a conffile, so if you make changes to it, it will be asked what you
> want to do.

I know this. But if upgrade is automated (as it is in my case)
this cause creation lot of *.dpkg-dist files that should be then
revised to edit old conf files. There is good practice used by
many honor package maintainers to separate config supplied by
package from user config.

> Which has nothing to do with his problem.

With -u option ntpdate-debian return zero and script
/etc/network/if-up.d/ntpdate will not be interrupted.

In any case this problem should be solved on the package level
as it was raised from recent ntp upgrade. ntpdate are used in
many scripts and this problem lead to endless multiply 

/bin/sh /etc/network/if-up.d/ntpdate
\_ lockfile-create /var/lock/ntpdate

processes running simultaneous as well as it deluge the log
files by lot of "lockfile creation failed" messages.

There was no problem with port for me never before as soon as I
am using -u option. But if You want to solve some problem You
should not do this by replacing old problem with new problem.
This is wrong way of upgrade.


**********************************
****   Vladimir Stavrinov   ******
*******   vs at inist.ru   **********
*****   http://inist.ru/   *******
**********************************






More information about the pkg-ntp-maintainers mailing list