Why is the systemd start timeout 30min?

[kaysond]

open-cas-linux/utils/open-cas.service

Lines 18 to 19 in 05b110f

	ExecStart=/sbin/casctl settle --timeout 1780 --interval 5
	TimeoutStartSec=30min

This seems unnecessarily long. If there's an issue on startup, you're stuck waiting 30min for this to time out so you can even get into a shell, or you have to play tricks with the kernel arguments to get systemd to allow a shell by other means.

Looking at the commits from the blame, it's not clear why it was made so long. Most systemd services are 1.5min because that's the default.

[jfckm]

Hi @kaysond, it sure is a long wait for timeout. I believe the change was made in response to some issues during our internal testing, but we also had reports such as #537. It was meant to be a stop-gap at the time as we developed something that could handle such cases asynchronously without holding up the boot process, but as you can see it didn't yet materialize.

[kaysond]

Hi @kaysond, it sure is a long wait for timeout. I believe the change was made in response to some issues during our internal testing, but we also had reports such as #537. It was meant to be a stop-gap at the time as we developed something that could handle such cases asynchronously without holding up the boot process, but as you can see it didn't yet materialize.

Seems like that should've been solved with something like this instead?

After=systemd-udevd.service
Wants=systemd-udevd.service

I think having a 30min timeout is a mistake :)