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 sure ExecStart= can be overrode.

On Sun, 16 Apr 2023 at 18:52, J <grandmastertrip...@gmail.com> wrote:

> 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 `. /lib/lsb/init-functions`
> in  `/etc/init.d/unbound` which is obviously not what I want to do
>
> On Sun, 16 Apr 2023 at 18:48, Debian Bug Tracking System <
> ow...@bugs.debian.org> wrote:
>
>> Thank you for filing a new Bug report with Debian.
>>
>> You can follow progress on this Bug here: 1034494:
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034494.
>>
>> This is an automatically generated reply to let you know your message
>> has been received.
>>
>> Your message is being forwarded to the package maintainers and other
>> interested parties for their attention; they will reply in due course.
>>
>> Your message has been sent to the package maintainer(s):
>>  unbound packagers <unbo...@packages.debian.org>
>>
>> If you wish to submit further information on this problem, please
>> send it to 1034...@bugs.debian.org.
>>
>> Please do not send mail to ow...@bugs.debian.org unless you wish
>> to report a problem with the Bug-tracking system.
>>
>> --
>> 1034494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034494
>> Debian Bug Tracking System
>> Contact ow...@bugs.debian.org with problems
>>
>

Reply via email to