[pkg-ntp-maintainers] Bug#793745: Bug#793745: ntp fails to start

[Bob Proulx]

Christophe Wolfhugel wrote:
> Kurt Roeckx wrote:
> > Do you use the default ntp.conf as shipped in the latest package?
> > If not can you either try that or add "rlimit memlock 0" at the
> > top of ntp.conf?
> 
> Good hit Kurt.
>
> No I do not use the stock ntp.conf ...

Same here.  I have the exact same results as Christophe reports.  The
problem is the requirement for "rlimit memlock 0" to be present in the
configuration file.  That wasn't needed previously.

> I would conclude that "something somewhere" makes the getpw*
> call fail when "rlimit memlock 0" is not used.

Yes.  As it is now anyone who upgrades and keeps their previously
working ntp.conf file will find the daemon unable to start.  I think
any option that is required is no longer optional. :-(

Michael Stone wrote:
> Based on the conversations upstream, I'd say that rlimit memlock 0
> should be the default in debian, not something that needs to be added
> to working configs.  ...

Agreed.

Bob