RunLast blocks drive decryption about runlast HOT 1 CLOSED

Hi @Kurisutian :)

When RunLast appears to have stalled, it's because its waiting for one of your user scripts to exit. You'll need to find which one is hanging. Make use of RunLast's log file, and don't be shy about making your scripts create their own logs too.

Launching a daemon that doesn't disconnect from the current tty is probably the most likely cause of a hanging condition.

Important note: the QTS environment during startup (when RunLast executes your scripts) is also not the same as after startup has completed. A script may work just fine when run manually at the CLI, but throw errors when running via RunLast due to not being attached to a terminal, $PATH incorrect, binaries unavailable, etc...

There's not-a-lot I can do to ensure RunLast completes startup with a hanging user script, except to background all script jobs. This won't fix your issue however. Your script would still contain a condition causing it to stall or fail to exit.

Hope this helps. I really should create a wiki page for this info.

from runlast.