Transcript:

Two panel meme.

Top panel: Woman in the front seat of a car screaming at a child in the rear seat. She’s saying “Why can’t you just shutdown?”

Bottom panel: A child screaming “A stop job is running for Session c2 of user … (1:30 / no limit)”

  • Venia Silente@lemmy.dbzer0.comEnglish
    91·
    1 day ago

    If it was really the program’s fault, why doesn’t it happen when I switch to sysvinit? (or maybe openrc, I haven’t tried that one)

      • lambisio@feddit.clEnglish
        2·
        5 hours ago

        Not onl that but they usually remove the init script as well, so unless you go for archives you no longer have a sane mechanism for starting and stopping the service.

        Fortunately Debian has a orphaned-init-scripts package that can help alleviate that pain, as you can also use those scripts (or even better, openrc scripts) as skeletons to replace systemd service units.

    • Björn@swg-empire.de
      123·
      1 day ago

      Because you didn’t bother fixing the underlying issue but got lucky.

      Or these other inits are more brutal in their shutdown procedure, but I doubt that.

      • Venia Silente@lemmy.dbzer0.comEnglish
        33·
        20 hours ago

        What “underlying issue”? The one in systemd?

        Everything works correctly (starting, shutting down under openrc / under sysvinit / manually / with killall)… except specifically systemd.