On 03/06/2018 09:45 PM, Udo van den Heuvel wrote:
> # cat 10-environment.conf
> ExecStart=
> EnvironmentFile=-/etc/sysconfig/ntpd
> ExecStart=/usr/sbin/ntpd -u ntp:ntp $OPTIONS
I gave this concept a try. We were missing the [Service] section header.
Use this instead:
[Service]
ExecStart=
Environm
On 06-03-18 21:09, Richard Laager wrote:
> Previously, you could not override ExecStart, only add to it. In systemd
> 197 (available in Fedora 18), this syntax should work:
>
> ExecStart=
> EnvironmentFile=-/etc/sysconfig/ntpd
> ExecStart=/usr/sbin/ntpd -u ntp:ntp $OPTIONS
>
> The empty ExecStart
I tried this to security-discuss, but I'm not sure if it went through:
The Debian security team has asked me which of the February 2018
ntp-4.2.8p11 vulnerabilities apply to NTPsec:
http://support.ntp.org/bin/view/Main/SecurityNotice#Recent_Vulnerabilities
--
Richard
___
On 03/06/2018 09:06 AM, Udo van den Heuvel wrote:
> I must look into this way of solving things as it did not work for me yet.
> I installed the default ntpd.service file.
> Then in /etc/systemd/system/ntpd.service.d/ I created
> 10-environment.conf with contents:
> EnvironmentFile=-/etc/sysconfig
On 06-03-18 05:04, Richard Laager wrote:
> On 03/05/2018 08:06 AM, Udo van den Heuvel wrote:
>> How can we please get these lines in the ntpd.service file?
>>
>> EnvironmentFile=-/etc/sysconfig/ntpd
>> ExecStart=/usr/sbin/ntpd -u ntp:ntp $OPTIONS
>>
>> and of course:
>>
>> # cat /etc/sysconfig/ntpd
Is something interesting going on here, or is this just leftover cruft?
Why would ntp_adjtime turn into SIGSYS? Would that be mentioned in a man
page? Do we care about running on those systems?
/*
* Use sigsetjmp() to save state and then call ntp_adjtime(); if
* it f
