Thanks for that. It looks like the builtin systemd umount.target is trying to unmount /afs before or in parallel with the openafs-client.service commands to unmount /afs, which is not the desired ordering. We should be able to specify Before=umount.target in openafs-client.service to get a different behavior. (I'm not confident enough in my understanding of systemd yet to claim that this should fix the issue.)
If you want, you can copy /lib/systemd/system/openafs-client.service to /etc/systemd/system and make that change locally (the /etc version overrides the /lib version), but I will try to get this in a new upload as well. I'm still confused by the lines: nov 04 18:15:36 kingdom-play systemd[1]: user@5000.service stop-sigterm timed out. Killing. nov 04 18:15:36 kingdom-play systemd[1]: Stopped User Manager for UID 5000. nov 04 18:15:36 kingdom-play systemd[1]: Unit user@5000.service entered failed state. which account for more than a minute of the delay, but the larger portion of the delay seems attributable to the bits which are obviously AFS-related. I did find http://forums.fedoraforum.org/archive/index.php/t-298680.html , which seems to implicate an rc.local file. Do you have one in place? -Ben -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
