Re: xntp mlockall issue patched yet?
On 2017-07-07, Kaya Samanwrote: >>> ntpd 4.2.8p10@1.3728-o Fri Jun 2 02:18:56 UTC 2017 (1): Starting > > The exact problem is that the service doesn't start... I have disabled > the ntpd from base in rc.conf then execute the rc.d script and no > service?? - just the error above. > > The service is added in rc.conf.local as such: > > xntpd=YES > xntpd_flags="" That's not the way xntpd is enabled. You may want to use rcctl(8): # rcctl stop ntpd ntpd(ok) # rcctl disable ntpd # rcctl enable xntpd # rcctl start xntpd xntpd(ok) The relevant lines in /etc/rc.conf.local end up being this: ntpd_flags=NO pkg_scripts=xntpd -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: xntp mlockall issue patched yet?
On 07/07/2017 10:11 PM, Allan Streib wrote: Kaya Samanwrites: I'm running current (6.1 GENERIC.MP#99 amd64) and keep getting this message when trying to start ntp from @ports: ntpd 4.2.8p10@1.3728-o Fri Jun 2 02:18:56 UTC 2017 (1): Starting mlockall(): Cannot allocate memory fatal out of memory (32 bytes) Why not use ntpd(8), provided in the base install? Allan Yes, that would be fine however, I am running some scripts which need the output of the ntpq command which is part of xntp.
Re: xntp mlockall issue patched yet?
On 07/08/2017 12:11 AM, Christian Weisgerber wrote: On 2017-07-07, Kaya Samanwrote: I'm running current (6.1 GENERIC.MP#99 amd64) and keep getting this message when trying to start ntp from @ports: ntpd 4.2.8p10@1.3728-o Fri Jun 2 02:18:56 UTC 2017 (1): Starting mlockall(): Cannot allocate memory fatal out of memory (32 bytes) What exactly is your problem? The ntpd from the net/ntp port runs fine. It logs a harmless error "mlockall(): Cannot allocate memory", but this doesn't affect its operation. The exact problem is that the service doesn't start... I have disabled the ntpd from base in rc.conf then execute the rc.d script and no service?? - just the error above. The service is added in rc.conf.local as such: xntpd=YES xntpd_flags="" so it should just kick in as expected but it doesn't :-(
Re: xntp mlockall issue patched yet?
On 2017-07-07, Kaya Samanwrote: > I'm running current (6.1 GENERIC.MP#99 amd64) and keep getting this > message when trying to start ntp from @ports: > > ntpd 4.2.8p10@1.3728-o Fri Jun 2 02:18:56 UTC 2017 (1): Starting > > mlockall(): Cannot allocate memory > > fatal out of memory (32 bytes) What exactly is your problem? The ntpd from the net/ntp port runs fine. It logs a harmless error "mlockall(): Cannot allocate memory", but this doesn't affect its operation. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: xntp mlockall issue patched yet?
Kaya Samanwrites: > I'm running current (6.1 GENERIC.MP#99 amd64) and keep getting this > message when trying to start ntp from @ports: > > ntpd 4.2.8p10@1.3728-o Fri Jun 2 02:18:56 UTC 2017 (1): Starting > > mlockall(): Cannot allocate memory > > fatal out of memory (32 bytes) Why not use ntpd(8), provided in the base install? Allan