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
[–] 28 points 3 months ago (12 children)

Why? You can bypass it immediately if it's a one-off, or go update the unit configuration to have a short timeout if it's a regular error.

More likely though, it's something that should actually be fixed, like a misconfigured fstab. Systemd is rarely the problem here.

  • source
  • parent
  • hideshow 12 child comments
  • [–] 3 points 3 months ago (11 children)

    how do you bypass it? didn't know its a thing

  • source
  • parent
  • hideshow 11 child comments
  • [–] 8 points 3 months ago (7 children)

    If you hit Ctrl-Alt-Delete 7 times in 2 seconds it will skip immediately

  • source
  • parent
  • hideshow 7 child comments
  • [–] 9 points 3 months ago (5 children)

    I can't tell if you're fucking with us or not. πŸ˜’

  • source
  • parent
  • hideshow 5 child comments
  • [–] 2 points 3 months ago (4 children)

    Hard power off dont care, and neither do modern filesystems.

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

    Unless the culprit is that one process permanently stuck in uninterruptible disk sleep, in which case the timer would just perpetually go up, and pressing 7x Ctrl-Alt-Del as you mentioned will simply shut down systemd and the kernel itself will start complaining (faulty hardware can cause this)

  • source
  • parent
  • [–] 6 points 3 months ago (2 children)

    You can do systemctl edit <unit>. There you can override all options without changing the main unit file.

  • source
  • parent
  • hideshow 2 child comments