[Ovirt-devel] [PATCH]: Fix ovirt-identify-node to work at boot time

[Daniel P. Berrange]

On Thu, Jun 05, 2008 at 09:25:45AM +0200, Chris Lalancette wrote:
> Perry N. Myers wrote:
> >> That sounds right to me.  The only thing I was wondering about is doing this:
> >>
> >> - start libvirt
> >> - run node-identify as normal
> >> - restart libvirt service to pick up new keytab
> > 
> > We should try to avoid doing funky things with init sequences if possible, 
> > and starting/stopping libvirt would definitely be abnormal.
> > 
> > So the sequence that I outlined should be good as it doesn't require 
> > libvirt to be toggled like this.
> 
> Right.  I definitely agree with Perry on principal.  And, in practice, I
> couldn't get the quick "start libvirtd, collect info, restart" to work properly.
>  Although I do admit I didn't dig into it very deeply or for very long.

I must admit to being surprised that the restart is needed. The Kerberos
stuff is only used for TCP connections, while your node-identify bit is
connecting via the UNIX socket so should not be triggering Kerberos yet.
Guess it is possible that SASL loads this stuff only at startup rather
than when a client actually connects though.

Dan
-- 
|: Red Hat, Engineering, London   -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org  -o-  http://virt-manager.org  -o-  http://ovirt.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-  F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|