[Bug 483506] [NEW] karmic: /afs should be ready before gdm starts

[Russ Allbery]

Martin <martin at schwier.cc> 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 (rra at debian.org)               <http://www.eyrie.org/~eagle/>

-- 
karmic: /afs should be ready before gdm starts
https://bugs.launchpad.net/bugs/483506
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs at lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs