Re: [chrony-dev] Upstream systemd change to PIDFile location in service unit

[Bill Unruh <unruh@xxxxxxxxxxxxxx>]

On my systemd system (Mageia 6) it is /run/chrony.pid and
/run/chrony/chrony.sock
and /var/run points to /run

The /lib/systemd/system/chronyd.service file is

-----------------------------------
[Unit]
Description=NTP client/server
After=ntpdate.service sntp.service ntpd.service
Conflicts=ntpd.service systemd-timesyncd.service

[Service]
Type=forking
PIDFile=/var/run/chronyd.pid
EnvironmentFile=-/etc/sysconfig/chronyd
ExecStart=/usr/sbin/chronyd $OPTIONS
ExecStartPost=/usr/libexec/chrony-helper update-daemon

[Install]
WantedBy=multi-user.target
-------------------------------------------------------
And chrony starts up fine

On Mon, 15 Apr 2019, Miroslav Lichvar wrote:

> On Thu, Apr 11, 2019 at 11:05:37AM -0500, Troy Engel wrote:
> > Understood - in my humble opinion, it's a disservice to have the built-in
> > compiled directory be different than the example unit file, as if you just
> > compile it with the defaults but then change only the systemd unit the
> > process hangs when trying to (re)start it, as the app is creating the PID
> > file in a location different than where systemd is trying to look for it.
>
> If there is the /var/run -> /run compatibility symlink, I think it
> should work even in the default configuration.
>
> > Here's me changing just the unit file without the compiled-in directory:
> >
> > ====================
> > Apr 11 10:07:55 garage chronyd[6230]: chronyd version 3.4 starting (+CMDMON
> > +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND +ASYNCDNS +SECHASH +IPV6>
> > Apr 11 10:07:55 garage chronyd[6230]: Frequency -13.439 +/- 0.532 ppm read
> > from /var/lib/chrony/drift
> > Apr 11 10:07:55 garage systemd[1]: chronyd.service: Can't open PID file
> > /run/chronyd.pid (yet?) after start: No such file or directory
>
> Shouldn't it be opening /run/chrony/chronyd.pid?
>
> --

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