On Mon, 1 Dec 2014 21:54:08 +0100 Sjoerd Simons sjo...@luon.net wrote:
No pretty sure it was from v208 directly. I was just re-reading the code of
upstream system again it it looks like upstream now removes the old socket
file
right before calling bind:
On Thu, Nov 27, 2014 at 05:48:45PM +0100, Michael Biebl wrote:
Am 27.11.2014 um 16:41 schrieb Michael Biebl:
Am 27.11.2014 um 15:59 schrieb Michael Biebl:
I would have expected, that the socket does *not* exist before systemd
is re-execd, but apparently I had a file there:
srw-rw-rw- 1
Am 27.11.2014 um 15:59 schrieb Michael Biebl:
I would have expected, that the socket does *not* exist before systemd
is re-execd, but apparently I had a file there:
srw-rw-rw- 1 root root 0 Oct 10 10:41 /run/systemd/notify
and no process listening on it.
(don't worry about the date, it
Am 27.11.2014 um 16:41 schrieb Michael Biebl:
It's actually a bit simpler: v44 *did* already use /run/systemd/notify
(with permissions srw-rw-rw-), then it was changed to use an abstract
namespace and it was changed back and forth a couple of times.
Maybe a simple chmod will do when upgrading
Am 27.11.2014 um 16:41 schrieb Michael Biebl:
Am 27.11.2014 um 15:59 schrieb Michael Biebl:
I would have expected, that the socket does *not* exist before systemd
is re-execd, but apparently I had a file there:
srw-rw-rw- 1 root root 0 Oct 10 10:41 /run/systemd/notify
and no process
5 matches
Mail list logo
