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)"

you are viewing a single comment's thread
view the rest of the comments
[–] 8 points 3 months ago (4 children)

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)

  • source
  • parent
  • hideshow 4 child comments
  • [–] 10 points 3 months ago (1 child)

    possibly they ship a bad systemd unit config for their package

  • source
  • parent
  • hideshow 1 child comment
  • [–] 3 points 3 months 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.

  • source
  • parent
  • [–] 11 points 3 months ago (1 child)

    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.

  • source
  • parent
  • hideshow 1 child comment