On 19 June 2015 at 00:42, Ric Moore <wayward4...@gmail.com> wrote: > > > $ systemd-analyze critical-chain >> >> This will tell you what is taking a long time to start. >> > > > Thanks Ric. This helps and confuses.
I get this: └─shorewall.service @11.793s +1min 31.901s └─network-online.target @11.793s └─network.target @11.793s └─networking.service @4.239s +7.553s └─local-fs.target @4.239s └─run-user-132.mount @1min 48.874s └─local-fs-pre.target @2.132s └─systemd-remount-fs.service @2.033s +98ms └─keyboard-setup.service @1.374s +657ms └─systemd-udevd.service @1.365s +9ms └─systemd-tmpfiles-setup-dev.service @1.056s +307ms └─kmod-static-nodes.service @970ms +85ms └─system.slice @970ms └─-.slice @970ms How do I find out why run-user-132.mount takes 48.874s to finish? Regards Johann -- Because experiencing your loyal love is better than life itself, my lips will praise you. (Psalm 63:3)