Gerhardus Geldenhuis wrote:
Hi David,
According to my understanding that is correct. As in the hostname should
be on the localhost line. If you ip changed then you would have to
update that line if you do it as you have suggested. What I am still
trying to find a clear answer on is how do you handle multihomed hosts
and should the hostname in /etc/sysconfig/network really be set to the
fqdn? If you do that then it breaks the command hostname and you get the
same result using hostname and hostname -f. Hopefully someone else can
clear it up.
Regards
[...]
Thanks. So I can see why it might want to insert a single long line:
127.0.1.1 client1.my.domain client1 localhost ...
For our own use, I've written a small snippet that will do what we want;
that is, two separate lines:
127.0.0.1 localhost...
my.ip.num.ber client1.my.domain client1
and it works.
But I'm new to cobbler and snippets, so I think my implementation may be
poor. Whereas there are bash and python variables containing the
hostname, there doesn't seem to be a bash variable containing the client
IP number through which the kickstart is running. Comparing with
existing snippets, I found some python that loops through all
interfaces, getting the potential IP number of each. But I wonder if
there is a simple variable referring to the IP being used for the
client's end of the kickstart?
(Is such information documented somewhere? I'm happy to read manuals if
I know that such things exist!)
--
: David Lee
: ECMWF (Data Handling System)
: Shinfield Park
: Reading RG2 9AX
: Berkshire
:
: tel: +44-118-9499 362
: email: david.lee(a)ecmwf.int