| Re: [chrony-dev] [Regression 3.5 -> 4.0-pre1]: Could not remove /run/chronyd.pid : Permission denied |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
- To: chrony-dev@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-dev] [Regression 3.5 -> 4.0-pre1]: Could not remove /run/chronyd.pid : Permission denied
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Tue, 7 Apr 2020 16:37:45 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1586270271; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=IwzjS6e/dSCeAleIv29PTGA7MqMHNeIM2Sj0S7YMFD8=; b=YCh3jz5GQG+qGcOAqGeIzM+TfUgQpcFAOscxc4O0G5pmGZO8apWb/Ed0UHpgZEXSy50dRs V+7gbqTauALdUtIaGC1PSy72x/gY/uP3MDr+puNxWXOCClRIold2odSGsTGdnWe0DPqSHW 3q2j4qeFbjX+zp6WV5Xbz6avPbTdw7M=
On Tue, Apr 07, 2020 at 04:26:20PM +0200, Vincent Blut wrote:
> Hi,
>
> While preparing chrony 4.0-pre1 for Debian experimental, I observed that
> stopping chronyd throws the following error:
>
> chronyd[118401]: Could not remove /run/chronyd.pid : Permission denied
>
> I have yet to look for where the issue lies but as I’m unable to reproduce
> this with chrony 3.5, we probably have a regression here.
There might be two separate issues.
Does the Debian package override the default location of the pidfile?
Since 3.4 it should be in /var/run/chrony (or /run/chrony). When
chronyd dropped the root privileges, it couldn't remove a file in
/var/run (or /run). Previously the failure to remove the file
produced only a debug message. Now it's an error syslog message.
--
Miroslav Lichvar
--
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.