Quoting Russ Allbery <[email protected]>:
... The AFS file server depends on:
# Required-Start: $local_fs $remote_fs $network $time
It should also depend on $bind9, or at least the availability of a
name server. Right now, when my server machine -- which is the only
server on my network and also functions as a name server and Internet
gateway -- starts the "openafs-fileserver" script, the vlserver
refuses to start with this message:
vlserver: couldn't get address of this host (bitis).
It doesn't matter if I add a line like "192.168.2.10 bitis.umrk.nl"
to the machine's /etc/hosts file either (which should not be necessary
in any case): the vlserver still refuses to start.
Of course, later on when I start it manually the vlserver does not
give the same error, because by then the name server is available.
Finally, to verify this bug, I installed a second name server on the
network that was available as the openafs-fileserver script was run.
The result was indeed that the vlserver could start up without any
errors:
Thu Jul 22 00:34:26 2010 Using 192.168.2.10 as my primary address
Thu Jul 22 00:34:26 2010 Starting AFS vlserver 4 (/usr/lib/openafs/vlserver)
My apologies for not being more precise the first time around.
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
