On 2/16/21 5:07 PM, Jason Cooper wrote: > > I=E2=80=99ve been using Artix / runit for a few months now with great suc= cess. > Now I=E2=80=99m moving over some of my servers to Artix that run `cloudfl= ared`. > Sadly, this tool doesn=E2=80=99t have an option to disable backgrounding > (daemonizing). > > What=E2=80=99s the idiomatic way to handle such processes with runit? I= =E2=80=99d like to > do more than `/etc/rc.local`, and obviously less than full supervision > runit. How does everyone handle this situation? > > > > On Feb 16, 2021 at 11:17:54 AM, Armin wrote:
> You could see if it at least can write a PID file, or create a runit > service that "loses control" over the cloudflared child process. > Yeah, that=E2=80=99s what I=E2=80=99m leaning towards. A small tool that l= aunches the misbehaving process, and monitors `/proc/$pid` =E2=80=A6 I was just really = hoping not to have to write it :-)
In either way, that daemon should provide an option to not background. As > for cloudflared, I was not even able to start it backgrounded (it just ke= pt > running in the forground in my case), but I agree there should be an opti= on > for this - you should probably file a bug. >
I=E2=80=99ve been using Artix / runit for a few months now with = great success.=C2=A0 Now I=E2=80=99m moving over some of my servers to Ar= tix that run `cloudflared`.=C2=A0 Sadly, this tool doesn=E2=80=99t have an o= ption to disable backgrounding (daemonizing).
What=E2=80=99s the idiomatic way to handle such processes with runit?=C2=A0 I=E2=80=99d like to do more than `/etc/rc.local`, and = obviously less than full supervision runit.=C2=A0 How does everyone handle th= is situation?
>=C2=A0
"ltr" class=3D"gmail_attr" style=3D"">> On Feb 16, 2021 at 11:17:54 AM, = Armin <armin-at-systemausfall.or= g> wrote:
You could see if it at least = can write a PID file, or create a runit service that "loses control&qu= ot; over the cloudflared child process.
l_quote">Yeah, that=E2=80=99s what I=E2=80=99m leaning towards.=C2=A0 A sma= ll tool that launches the misbehaving process, and monitors `/proc/$pid` = =E2=80=A6 I was just really hoping not to have to write it :-)
In either way, that daemon should provide an option to not= background. As for cloudflared, I was not even able to start it background= ed (it just kept running in the forground in my case), but I agree there sh= ould be an option for this - you should probably file a bug.
On 2/16/21 5:07 PM, Jason Cooper wrote: > > I=E2=80=99ve been using Artix / runit for a few months now with great suc= cess. > Now I=E2=80=99m moving over some of my servers to Artix that run `cloudfl= ared`. > Sadly, this tool doesn=E2=80=99t have an option to disable backgrounding > (daemonizing). > > What=E2=80=99s the idiomatic way to handle such processes with runit? I= =E2=80=99d like to > do more than `/etc/rc.local`, and obviously less than full supervision > runit. How does everyone handle this situation? > > > > On Feb 16, 2021 at 11:17:54 AM, Armin wrote:
> You could see if it at least can write a PID file, or create a runit > service that "loses control" over the cloudflared child process. > Yeah, that=E2=80=99s what I=E2=80=99m leaning towards. A small tool that l= aunches the misbehaving process, and monitors `/proc/$pid` =E2=80=A6 I was just really = hoping not to have to write it :-)
In either way, that daemon should provide an option to not background. As > for cloudflared, I was not even able to start it backgrounded (it just ke= pt > running in the forground in my case), but I agree there should be an opti= on > for this - you should probably file a bug. >
I=E2=80=99ve been using Artix / runit for a few months now with = great success.=C2=A0 Now I=E2=80=99m moving over some of my servers to Ar= tix that run `cloudflared`.=C2=A0 Sadly, this tool doesn=E2=80=99t have an o= ption to disable backgrounding (daemonizing).
What=E2=80=99s the idiomatic way to handle such processes with runit?=C2=A0 I=E2=80=99d like to do more than `/etc/rc.local`, and = obviously less than full supervision runit.=C2=A0 How does everyone handle th= is situation?
>=C2=A0
"ltr" class=3D"gmail_attr" style=3D"">> On Feb 16, 2021 at 11:17:54 AM, = Armin <armin-at-systemausfall.or= g> wrote:
You could see if it at least = can write a PID file, or create a runit service that "loses control&qu= ot; over the cloudflared child process.
l_quote">Yeah, that=E2=80=99s what I=E2=80=99m leaning towards.=C2=A0 A sma= ll tool that launches the misbehaving process, and monitors `/proc/$pid` = =E2=80=A6 I was just really hoping not to have to write it :-)
In either way, that daemon should provide an option to not= background. As for cloudflared, I was not even able to start it background= ed (it just kept running in the forground in my case), but I agree there sh= ould be an option for this - you should probably file a bug.
