[OpenAFS] Client start issues

pod pod@herald.ox.ac.uk
Thu, 8 Sep 2005 23:14:11 +0100 (BST)

>>>>> "MS" == Madhusudan Singh <singh.madhusudan@gmail.com> writes:

    MS> The URL above suggests that this behaviour obtains if
    MS> AFS_CLIENT=true is not set in /etc/openafs/afs.conf.client, but
    MS> that is clearly not the case here.

    MS> What could be going on ?

On Debian (at least on sarge, probably also true for woody) the startup
scripts from the original openafs tarball, namely src/afsd/afs.conf.linux
and src/afsd/afs.rc.linux, are patched.

/etc/init.d/openafs-client (patched src/afsd/afs.rc.linux) sources
/etc/openafs/afs.conf (patched src/afsd/afs.conf.linux) which in turn
sources /etc/openafs/afs.conf.client.

Clearly /etc/init.d/openafs-client is not seeing AFS_CLIENT=true.

Just two of the many ways in which this might happen are if one of
/etc/openafs/afs.conf or /etc/init.d/openafs-client is somehow the
unpatched version:

 - unpatched /etc/openafs/afs.conf: you have a /etc/openafs/afs.conf which
   does not source /etc/openafs/afs.conf.client so AFS_CLIENT does not get

 - unpatched /etc/init.d/openafs-client: you have a 'is_on' sub that is
   looking for 'on'/'off' rather than the Debian version which looks
   for 'true'/anything.