On Fri, 12.02.16 23:51, Mikhail Kasimov (mikhail.kasi...@gmail.com) wrote: > > RuntimeMaxSec= just says "abort this shit if it takes longer than > > this". The usecase is to use it for stuff which is not supposed to > > take this long, and where it's better to abort it, and complain than > > to leave it running unbounded. > > Ok, got it. Thanks! And one more question -- will 'systemctl status' and > 'journalctl' contain the explanation about RuntimeMaxSec= limit overflow > in logs? E.g. "[FAILED] bla-bla-bla.service. Forced exit, because > RuntimeMaxSec limit is hit". Or something around this.
So, "systemctl status" first shows you the general unit status and then shows you recent log data from and about the unit. In the general unit status you find a short field explaining the cause for the failure, and for timeouts it will say "timeout" (but not be any more specific). In the log data you'll find a longer, human readable explanation. Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
