<html><head></head><body>Might have been a red herring <br><br><div class="gmail_quote">Am 28. November 2015 15:36:12 MEZ, schrieb Martin Pitt <mpitt@debian.org>:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">Hey Michael,<br /><br />Michael Biebl [2015-09-24 18:32 +0200]:<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"> Am 24.09.2015 um 17:46 schrieb hannu.tmp@pp.inet.fi:<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;"> This works for me:<br /> <br /> copy /lib/systemd/system/systemd-fsckd.service to /etc/systemd/system<br /> <br /> edit /etc/systemd/system/systemd-fsckd.service, add TimeoutStartSec under [Service]<br /> <br /> [Service]<br /> TimeoutStartSec=60min<br /></blockquote> <br /> Hm, good point. We should probably disable the Timeout completely like<br /> in systemd-fsck-root.service and systemd-fsck@.service by setting<br /> <br /> TimeoutStartSec=0<br /> <br /> The default is 90s, and an fsck for a large disk can certainly take<br /> longer for ext3.<br /></blockquote><br />Do you happen to know *why* this
works? fsckd.service is not a<br />Type=oneshot, and I don't see why the actual startup of the process<br />should take that long?<br /><br />Martin</pre></blockquote></div></body></html>