RE: [chrony-users] chrony-3.4 bug?

["LeBlanc, Daniel James" <daniel.leblanc@xxxxxxxxxxxxx>]

Hi Miroslav.

I thought that Type=forking would be required for the service to get started as root and then spawned off under the chrony user, but I just tested it and it appears to start under the chrony user in each case (Type=forking and Type=simple).

I have changed the unit file to Type=simple as you suggested.  I do understand that chrony executes only a single process.

If I now add the -n option, chronyd starts without incident.  That must have been the problem.

Thanks!

Dan LeBlanc


-----Original Message-----
From: Miroslav Lichvar [mailto:mlichvar@xxxxxxxxxx] 
Sent: November-02-18 3:38 PM
To: chrony-users@xxxxxxxxxxxxxxxxxxxx
Subject: Re: [chrony-users] chrony-3.4 bug?

On Fri, Nov 02, 2018 at 05:39:01PM +0000, LeBlanc, Daniel James wrote:
> [Service]
> ExecStart=/var/chrony/sbin/chronyd -4 -n -u chrony -f /var/chrony/etc/chrony.conf -l /var/chrony/log/chrony.log
> Type=forking

The -n option should be used with Type=simple as chronyd won't fork.
That's what you want, right?

Type forking with -n might explain the timeout, but I'm not sure why
chronyd wouldn't start at all. It's weird. Does it work in console?

-- 
Miroslav Lichvar

-- 
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx 
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx 
with "help" in the subject.
Trouble?  Email listmaster@xxxxxxxxxxxxxxxxxxxx.


--
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble?  Email listmaster@xxxxxxxxxxxxxxxxxxxx.