Bug#1034494: Acknowledgement (unbound: Unbound fails to create pid file even when pidfile specified in /etc/unbound/unbound.conf or /etc/init.d/unbound)

Thank you so much. Your help was amazing. Keep up the great work. Can close this report. On Tue, 18 Apr 2023 at 13:13, Simon Deziel wrote: > You can override ExecStart= by first defining it empty like that: > > [Service] > ExecStart= > ExecStart=/usr/sbin/unbound -d $DAEMON_OPTS > > HTH, >

Bug#1034494: Acknowledgement (unbound: Unbound fails to create pid file even when pidfile specified in /etc/unbound/unbound.conf or /etc/init.d/unbound)

You can override ExecStart= by first defining it empty like that: [Service] ExecStart= ExecStart=/usr/sbin/unbound -d $DAEMON_OPTS HTH, Simon On 2023-04-17 23:20, J wrote: Thank you so much, thats exactly what I was missing. I commented out the -p in ExecStart=/usr/sbin/unbound -d

Bug#1034494: Acknowledgement (unbound: Unbound fails to create pid file even when pidfile specified in /etc/unbound/unbound.conf or /etc/init.d/unbound)

Thank you so much, thats exactly what I was missing. I commented out the -p in ExecStart=/usr/sbin/unbound -d $DAEMON_OPTS in /usr/lib/systemd/system/unbound.service And now I have a pidfile back that I can use. Unless there is any better way? I tried to override the unbound.service but I'm not

Bug#1034494: Acknowledgement (unbound: Unbound fails to create pid file even when pidfile specified in /etc/unbound/unbound.conf or /etc/init.d/unbound)

Hi! I'm having an issue where unbound is not creating the pid file I've specified in unbound.conf `pidfile: "/run/unbound.pid"` I also see that this path is hard coded in `/etc/init.d/unbound` as `PIDFILE="/run/unbound.pid"` The only thing that fixes it is commenting out `.