On Sat, 6 Sep 2014, Kuklin István wrote: > Okay, if the bug has gone, I'll report it.
The 1.6.10-1 in unstable has a unit file for the client. (It also has a RC bug against it; stopping the client before taking the upgrade should be a valid workaround.) However, before you take the upgrade, I figured out (while reading up on systemd) how to collect the shutdown messages I was interested in. With systemd, the shutdown messages are logged in the "journal", which can be stored across boot, depending on the configuration of journald. In the default configuration, you need to create the directory /var/log/journal for the logs to be stored. Starting from the next boot after that, the logs should be kept, so after the following reboot (and hang), you can then use 'journalctl --full --system -b -1' to get logs from the previous boot and shutdown. I would be interested in seeing those, in the vicinity of the openafs-client shutdown messages, if you can. Thanks, Ben
