Re: Faster automatic shutdown

[Sean Atkinson <sean netproject com>]

Hi,

> 	If it said no value set for '/' - it must have gone over the network to
> get that answer; (surely), if so - it should do likewise when you log
> in.

I just tested it locally first but figured I'd get more exciting output.

Testing it across the network reveals an unexpected asymmetry between
the machines.  The server hosts /home, and the client mounts it over
NFS.  The server can access gconfd-2 running on the client fine,
reporting the same "No value set" as when running locally.  This is some
progress, at least.

However the client fails to access gconfd-2 when running on the server,
reporting a COMM_FAILURE.  The logs indicate this is because a second
gconfd-2 is started locally but exits since it fails to acquire the lock
over NFS.  As far as I can tell NFS locking works - the services are
running, and desktop login seems fine.  I guess the client machine isn't
connecting to the server's gconfd-2 for some reason, so it goes on to
try a starting it locally.

> 	Sure; you can do a load of ORBit_small_listen_for_broken stuff in
> gconfd on the client handles, and track when they go away. Ultimately
> though, I'd try to fix the underlying problem. FWIW it works just fine
> here I was logging into my RH8 laptop and my RH9 workstation as the same
> user sharing the same gconfd-2 instance over the network only a few days
> ago.

Hmm...  This makes me suspicious that something wacky's going on.  I
thought I saw the problem disappear between Red Hat 8.0 and 9, so I was
disappointed when it came back to bite me recently.

Cheers,

Sean.

-- 
Sean Atkinson <sean netproject com>
Netproject