On 19. 10. 24 12:23, Arthur de Jong wrote:
Thanks for all the testing. I've uploaded 0.9.12-9 to unstable which
should hopefully migrate to testing soon.
Thanks! I can confirm that now nslcd does start correctly out of the box
in an Incus container with trixie.
On Fri, 2024-10-18 at 21:41 +0200, David Koňařík wrote:
> Yes, with this set nslcd does start.
Thanks for all the testing. I've uploaded 0.9.12-9 to unstable which
should hopefully migrate to testing soon.
--
-- arthur - art...@arthurdejong.org - https://arthurdejong.org/ --
signature.asc
Des
On 18. 10. 24 12:52, Arthur de Jong wrote:
Can you check if this works:
ProtectSystem=strict
ReadWritePaths=/run
(if possible I'd like to keep strict over full)
Yes, with this set nslcd does start.
Control: severity -1 important
On Wed, 2024-10-16 at 23:21 +0200, David Koňařík wrote:
>
> Setting "RuntimeDirectory=nslcd" instead still doesn't work, but now
> nslcd complains instead that "bind() to /var/run/nslcd/socket failed:
> Permission denied".
That is probably because systemd creates t
On 16. 10. 24 19:45, Arthur de Jong wrote:
On Wed, 2024-10-16 at 15:40 +0200, David Koňařík wrote:
As far as I can tell, this is because the packaged systemd service
sets "ProtectSystem=strict", which remounts everything read-only,
including the PID file directory. I fixed this by setting
"Prote
On Wed, 2024-10-16 at 15:40 +0200, David Koňařík wrote:
> As far as I can tell, this is because the packaged systemd service
> sets "ProtectSystem=strict", which remounts everything read-only,
> including the PID file directory. I fixed this by setting
> "ProtectSystem=full"; "ReadWritePaths=/run"
Package: nslcd
Version: 0.9.12-8
Hi all,
I just created an Incus container with Debian trixie and installed
nslcd. Sadly the default systemd service failed to start with the
following log:
mkdir: cannot create directory ‘/run/nslcd’: Read-only file system
chown: cannot access '/run/nslcd': No
7 matches
Mail list logo
