Conversation

Notices

1. Embed this notice
   mhoye (mhoye@mastodon.social)'s status on Wednesday, 22-Nov-2023 07:03:31 JST mhoye

   Linux nerds, is there a way to convince dbus to _shut down_ services that it has started up when the thing that started it up is no longer running?

   (and if it's easy, why is this not the default)

   • Embed this notice
     gnutelephony (gnutelephony@floss.social)'s status on Wednesday, 22-Nov-2023 07:03:31 JST gnutelephony

     in reply to

     @mhoye I recall a complex scheme done with systemd triggers. But yes, the idea that if X goes down, Y should too, should have been something easy to do, rather than fixing non-existing problems in other tooling.

   • Embed this notice
     Chris Siebenmann (cks@mastodon.social)'s status on Wednesday, 22-Nov-2023 07:16:58 JST Chris Siebenmann

     in reply to

     @mhoye I think it's not dbus directly making the decisions there; instead I think there's some systemd magic to listen for dbus requests and then start things to answer them. Systemd also has a system to shut down 'inactive' things, but I don't know if it can tell whether a dbus thing is genuinely inactive, and some daemons will shut themselves down.

     (If you think this can all go terribly wrong, yes, yes it can. Especially if things are not quite set right. We had fun experiences.)

     Haelwenn /элвэн/ :triskell: likes this.