Comment 1 for bug 483506

Martin <email address hidden> writes:

> The use of a legacy init script in openafs-client leads to the situation
> that on boot-up, /afs is not necessary ready before the gdm screen
> starts. This is a problem because our users home directories are in
> /afs. So if I log in after boot-up there is no writable home directory
> which results in many annoying error messages. I have to switch to a
> virtual terminal, log in, become root and restart gdm then.

> Is there anything I can do to fix this issue?

I wonder if AFS should provide $remote_fs, which will force it to be
started prior to anything that declares a dependency on $remote_fs. Now
that afsd has been moved to /sbin, I think that should work properly.
Currently it wants $remote_fs started before it runs, although doesn't
require it.

Ah, yes, the problem at present is that fs is in /usr/bin, not in /bin, so
things like setting the sysname and enabling setcrypt won't work if /usr
isn't available.

I wonder if I should move fs into /bin. Hrm.

--
Russ Allbery (<email address hidden>) <http://www.eyrie.org/~eagle/>