* Arthur de Jong [2017-06-25 12:50:13 +0200]:
> Another issue is that if a daemon crashes there certainly is a bug
> somewhere. If the service is silently restarted on crashes the bug will
> less likely be reported and fixed leaving a bug around longer.
For what it's worth,
segfault at 10 ip 7
* Arthur de Jong [2017-06-25 12:50:13 +0200]:
> Thanks for your service description. I am a bit reluctant to add
> restart-on-crash to nslcd and it could be a security risk in general
> for daemons.
>
> One reason for this is that it potentially turns a denial of service
> vulnerability into somet
On Sat, 2017-06-03 at 14:12 +, Sergio Gelato wrote:
> I've now successfully tested the fix from #827444 on both jessie and
> stretch.
>
> Specifically, I created
> /etc/systemd/system/nslcd.service.d/forking.conf with the following
> contents:
>
> [Service]
> Type=forking
> PIDFile=/var/run/n
I've now successfully tested the fix from #827444 on both jessie and stretch.
Specifically, I created /etc/systemd/system/nslcd.service.d/forking.conf with
the following contents:
[Service]
Type=forking
PIDFile=/var/run/nslcd/nslcd.pid
RemainAfterExit=no
Restart=on-failure
To test one can simpl
Package: nslcd
Version: 0.9.4-3+deb8u2
As noted in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851134#5,
"When it crashes, systemd does not automatically restart the process,
which may be a separate issue."
I can confirm this. I've seen nslcd crash (with different symptoms than in
#851134:
5 matches
Mail list logo
