On Fri, 6 Jul 2007, Debreczeni Gergely wrote:
> Hi !
>
> We were fixing this bug:
>
> https://savannah.cern.ch/bugs/index.php?24765
>
> and I beleive that this is valid, so hostname -f should return with a FQDN.
>
> Many YAIM function assumes that hostname -f is the FQDN,
> that's why we check at the beginning.
> But why it is not a FQDN in your case ? It should be, may you should
> correct your /etc/hosts file.
>
> Gergo
The WNs may be on a private network without (pseudo) domain defined.
If nothing else has a problem with that, YAIM should not require
the WNs to have a domain either. An exception can be made for WNs.
The bug referred to a server node (DPM), where it does matter.
> [log in to unmask] a écrit :
> > On Thu, 5 Jul 2007, Ilja Livenson wrote:
> >
> >> Hi, All
> >>
> >> I'm trying to install WN under SLC4 according to
> >> http://igrelease.forge.cnaf.infn.it/doku.php?id=doc:guides:install-wnslc4 .
> >> However, I've stumbled upon this a bit strange requirement of the yaim:
> >>
> >> # Checks if 'hostname -f' returns a fully qualified hostname. This is
> >> important.
> >> if ( ! hostname -f | grep '\.' > /dev/null ); then
> >> yaimlog ERROR "The hostname -f command does not return with a fully
> >> qualified hostname,";
> >> yaimlog ERROR "however this is necessary for YAIM to run properly.";
> >> yaimlog ERROR "Please check your /etc/hosts file ! Exiting.";
> >> exit -1
> >> fi
> >>
> >>
> >> Could anyone explain me why is it important for the WN to have a FQDN?
> >
> > As far as I can see it does not matter on a WN. CC YAIM developers.
> >
> >> And if it's not, can I simply comment out the check?
> >
> > Yes, give that a try.
> >
>
|