My always plugged in HDD with bees on it does that. 1 minute to shutdown at least because there’s always some kind of extend read or dedupe that need a sync.
… I brought this upon myself so I don’t have to complain.
I think that depends on the setting, I had situations where one of my docker containers took ages to shutdown and it would just say 00/02 00s but when it reached that limit, it would just go up.
A stop job is running(X time / 1:30) but the second time will be extended indefinitely for some fucking reason.
Alt-SysRq-i, u, oI don’t have time for this shit.
have i learned a new magic combo?!
Yes but no, u can in config file of systemd change timeout to 5,10 second or other number of seconds which u wish before it will kill it
My always plugged in HDD with bees on it does that. 1 minute to shutdown at least because there’s always some kind of extend read or dedupe that need a sync.
… I brought this upon myself so I don’t have to complain.
At least it tells you how long it’ll take before it decides to SIGKILL whatever is holding the shutdown sequence.
I think that depends on the setting, I had situations where one of my docker containers took ages to shutdown and it would just say 00/02 00s but when it reached that limit, it would just go up.
Individual services can override the default 90 seconds timeout. But then you can override their override if you think you are smarter, of course.
Well you say that, but I’ve seen the countdown go past and then reset to a higher number often.
I entrust you with this horror, go figure out what to blame.
shutdown-analyze.sh
#! /usr/bin/env bash shutdown_start=$(journalctl -b -1 -u systemd-logind --grep="System is (powering down|rebooting)" --output=cat --no-pager --output-fields=_SOURCE_REALTIME_TIMESTAMP) shutdown_start=$((shutdown_start / 1000000)) units=$(journalctl -b -1 --since=@$shutdown_start --output=cat --no-pager --output-fields=UNIT JOB_TYPE=stop CODE_FUNC=job_emit_start_message) for u in $units; do stopping_start=$(journalctl -b -1 --since=@$shutdown_start -u "$u" --output=cat --no-pager --output-fields=_SOURCE_REALTIME_TIMESTAMP JOB_TYPE=stop CODE_FUNC=job_emit_start_message _SYSTEMD_UNIT=init.scope) stopping_end=$(journalctl -b -1 --since=@$shutdown_start -u "$u" --output=cat --no-pager --output-fields=_SOURCE_REALTIME_TIMESTAMP JOB_TYPE=stop CODE_FUNC=job_emit_done_message _SYSTEMD_UNIT=init.scope) duration_human=$(systemd-analyze timespan $((stopping_end - stopping_start))us | tail -1 | sed 's/.*: //') printf "%s\t%10s %s\n" $((stopping_end - stopping_start)) "$duration_human" "$u" done | sort -rn | cut -f 2Similar to angry parents.