Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <CAEU5HDZD-U7vrQrusZxYW7L4wPiZL5m2kZw0nDz401oJjiVs=w@mail.gmail.com>
 <CABBYNZ+c1CfDDQ7GbO5wdQvF-ef=jaVKDcGGnVxHhJN84Edm5Q@mail.gmail.com>
 <CAEU5HDZVY7hYAK=1FhzSabg9n5Oogq81GqvsuHHJYU7Mr2TXUA@mail.gmail.com> <CABBYNZLLTfu33iU2Z+hE7R3sDyb+nnGSsmf1tiRva5A2TS1+8A@mail.gmail.com>
In-Reply-To: <CABBYNZLLTfu33iU2Z+hE7R3sDyb+nnGSsmf1tiRva5A2TS1+8A@mail.gmail.com>
From:   Dynastic Space <dynasticspace@gmail.com>
Date:   Thu, 20 Jul 2023 21:50:37 +0300
Message-ID: <CAEU5HDbRGW5-i2o=39p_Jfr5ET8ShkPtOsOjR2LyVa7Rn3gknw@mail.gmail.com>
Subject: Re: Daemonizing bluetoothd
To:     Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc:     linux-bluetooth@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

The bluez version that I am using is 5.56.
It's not that I had a problem: I just expected to see a daemon call,
and when I hadn't I was surprised. Then I started suspecting that
procd forks the process by itself, but I wasn't sure.
Your answer clarifies things for me. Thanks!

On Thu, Jul 20, 2023 at 9:33=E2=80=AFPM Luiz Augusto von Dentz
<luiz.dentz@gmail.com> wrote:
>
> Hi,
>
> Can't recall when we made the change to stop forking, but it has been
> a while bluetoothd has this behavior, doesn't procd handle processes
> that don't fork by themselves? How old is bluetoothd in OpenWRT that
> this is only showing up now?
>
> On Thu, Jul 20, 2023 at 11:15=E2=80=AFAM Dynastic Space <dynasticspace@gm=
ail.com> wrote:
> >
> > Thank you for your reply.
> > So you are saying that you are relying on whatever service manager to
> > daemonize the process? I am compiling for OpenWRT which uses procd,
> > not systemd.
> >
> > On Thu, Jul 20, 2023 at 9:04=E2=80=AFPM Luiz Augusto von Dentz
> > <luiz.dentz@gmail.com> wrote:
> > >
> > > Hi,
> > >
> > > On Thu, Jul 20, 2023 at 10:42=E2=80=AFAM Dynastic Space <dynasticspac=
e@gmail.com> wrote:
> > > >
> > > > I am reading through the bluetoothd code for version 5.56, but I
> > > > cannot find the call that makes it into a daemon. I don't see a for=
k
> > > > or a daemon call. How is it turned to one?
> > > > I am compiling the code on an OpenWRT system.
> > >
> > > We don't call fork anymore, since most likely bluetoothd would be run
> > > as a systemd service I don't think it matters though.
> > >
> > > --
> > > Luiz Augusto von Dentz
>
>
>
> --
> Luiz Augusto von Dentz