On Tue, 25 Nov 2014, Wolfgang Scheicher wrote: > On Monday 24 November 2014 13:43:55 Benjamin Kaduk wrote: > > Can you please provide the contents of /var/cache/openafs-client/*.env ? > > Sure. On my Desktop i have this: > # openafs-client.env > AFSD_ARGS= -dynroot -fakestat > AFS_SETCRYPT=off > AFS_SYSNAME=-help > KMOD=openafs > # openafs-client.shutdown.env > KMOD=openafs > > I also have a Live-System for a USB-Stick with this: > # openafs-client.env > AFSD_ARGS=-memcache -dynroot -fakestat > AFS_SETCRYPT=on > AFS_SYSNAME=-help > KMOD=openafs > # openafs-client.shutdown.env > KMOD=openafs > > I now also checked and compared several machines (i have some not that up to > date jessie machines and i figured out that on one of them there was a > functional openafs-client 1.6.10-2), and this is what i found: > On that machine AFSD_ARGS also contained -afsdb ! > ( AFS_AFSDB=true in /etc/openafs/afs.conf.client ) > Seems i missed that earlier when trying different settings. > > Now i need to figure out if i had a good reason for AFSD_ARGS=false ...
Okay, so this does look like the RemainAfterExit issue I had mentioned. You can check by copying /lib/systemd/system/openafs-client.service to /etc/systemd/system/openafs-client.service and adding a line RemainAfterExit=true in the [Service] section. Note that the presence of that file will prevent you from receiving future updates to the unit file from the packaging, so maybe it's best to only use it as a temporary measure. Enabling afsdb via debconf (dpkg-reconfigure openafs-client) should also be a usable workaround. I'll see about pushing the RemainAfterExit fix to unstable soon; sorry it's taken so long. -Ben -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
