[OpenAFS] Boot sequence OpenAFS/ GDM

Jukka Tuominen jukka.tuominen@finndesign.fi
Thu, 17 Oct 2013 22:00:31 +0300 (EEST)

Thanks Brandon,

your solution worked. However, if I plugged off network, I couldn't log
into local/unix account. Ideally, afs could wait for the network max 5
seconds (less if found earlier), and then release the thread and continue
waiting on the background.

I don't know scripting that well, but for the time being, I just added a
dumb 5 second delay before gdm starts.

If anybody can suggest a script like this, I'd be grateful. It probably
wouldn't hurt to make it even the default feature, since there were quite
a lot of similar symptoms out there while googling around. Also, I've
noticed that logging into local account when off-line is very slow with
afsd around. Maybe this kind of "wait >> release and continue waiting on
the background" approach could speed up things when off-line?

br, jukka

> On 10/17/13 07:49, "Jukka Tuominen" <jukka.tuominen@finndesign.fi> wrote:
>>I found some discussions about this issue on the net, but not a solution
>>that would work. I wonder if there's a speed-independent way to get the
>>boot sequence right every time?
> This is done by boot dependencies, and the details can differ between
> operating systems and distributions. However, it requires that the AFS
> startup script be modified so that it only exits after AFS is running,
> instead of the standard behavior where afsd is sent into the background
> to
> wait for network.
> The cheaty way to do this is to add something like
>     while sleep 5; do
>         test -d /afs/grand.central.org/service && break
>     done
> to the startup phase, to wait until we can reach something (you may want
> to use a path in your local cell) before returning control to the startup
> manager; then you can make the gdm startup depend on afs.
> --
> brandon s allbery kf8nh    sine nomine associates
> allbery.b@gmail.com       ballbery@sinenomine.net
> unix, openafs, kerberos, infrastructure, xmonad
> :��