Bug#793745: [pkg-ntp-maintainers] Bug#793745: [PATCH] I'm seeing it too.
On Sun, Aug 02, 2015 at 03:22:27PM -0400, sacrificial-spam-addr...@horizon.com wrote: Since I run a pool server, I have a customized config. That means that I have the pool servers commented out, and the comment on the rlimit command says it's not needed in that case, so I left it out of my config. Maybe the comment is a little misleading. There have been various reports over the past few year about the rlimit breaking things, but ussually dieing after a few hours of running or something like that. With the pool command it just doesn't start (for me). Maybe other see different kinds of error like the getpwuid() fail instead. Kurt -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793745: [pkg-ntp-maintainers] Bug#793745: [PATCH] I'm seeing it too.
Maybe the comment is a little misleading. How about # Preventing ntpd from swapping (with mlockall()) reduces time delays, # but resource limits (ulimit -l) cause out-of-meory errors that lead to # ntpd quitting with strange (or no) error messages. Particular trouble # spots are the -u option (depending on /etc/nsswitch.conf) and the pool # command (which does DNS lookups at run time). It's more reliable with # this disabled. # # Note that the busier your NTP server, the less swapping is a concern # in the first place. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
