Bob Proulx wrote:
Do you have the bug number handy? I would be interested in reading
through it.
Certainly:
- Debian Bug #609851 - incorrect variables used to set hostname in
dhclient-script
- http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=609851
I haven't noticed any behavior
John Hasler writes:
Ok. Is the idea to image all the machines identically and then
configure them automatically via dhcp? If so why do they need locally
configured hostnames at all?
By default all of our distribution templates set the hostname of the
system, via DHCP, to match the default
Bob Proulx wrote:
Tim Heckman wrote:
Luckily the two of these issues won't come in to play here. This is
going to be used on a system that does not have X installed and will
have a static IP address. We use DHCP to assign the address as it
is easier to deploy a new distribution for our
Tim Heckman wrote:
Bob Proulx wrote:
Tim Heckman wrote:
The last time dhclient was attempted with this would have been on
Debian 5.0. In our most recent Debian 6.0 template someone decided
to use dhcpcd,
What were they using before?
In Debian 5.0 dhcp3-client was the package
Tim writes:
The $new_host_name variable is the hostname that was provided by the
dhcp server.
Ok. Is the idea to image all the machines identically and then
configure them automatically via dhcp? If so why do they need locally
configured hostnames at all?
--
John Hasler
--
To UNSUBSCRIBE,
set DELAYLOGIN=yes in /etc/default/rcS.
--
John Hasler
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87obvzx1yu@thumper.dhh.gt.org
John,
Thank you for replying back as well as the idea to set this option. I
wish it had been this easy but it appears that this option does not
affect how getty prints the login prompt.
I believe this may only affect someone trying to log in and not how it
prints. If you have any further
John,
Thank you for replying back as well as the idea to set this option. I
wish it had been this easy but it appears that this option does not
affect how getty prints the login prompt.
I believe this may only affect someone trying to log in and not how it
prints. If you have any further
Tim Heckman wrote:
I have an interesting problem that should actually be seen as a compliment
to Debian. My system is booting so fast that the /sbin/getty is spawning
before DHCP sets the hostname. So I get a prompt like this:
Debian GNU/Linux 6.0 (none) hvc0
(none) login:
Bob Proulx wrote:
Am I correct in assuming that you have modified /sbin/dhclient-script
to set the hostname from the dhcp'd hostname? (That is what I did
when I was doing this.)
I've created a dhclient-exit-hook script to handle the processing. This
checks whether the hostname should be
Tim Heckman writes:
I've created a dhclient-exit-hook script to handle the processing.
This checks whether the hostname should be set and completes the
process. Only sets it if it really is needed.
Try killing getty in your script (init will respawn it). You may also
need to delay logins so
John Hasler writes:
Tim Heckman writes:
I've created a dhclient-exit-hook script to handle the processing.
This checks whether the hostname should be set and completes the
process. Only sets it if it really is needed.
Try killing getty in your script (init will respawn it). You may
also need
Tim Heckman wrote:
I've created a dhclient-exit-hook script to handle the processing.
This checks whether the hostname should be set and completes the
process. Only sets it if it really is needed.
Ah, very good. In this case it is six of one and a half dozen of the
other. Either way should
Tim Heckman wrote:
John Hasler writes:
Try killing getty in your script (init will respawn it). You may
also need to delay logins so that the user can't log in too early.
I'm not sure why but I hadn't thought of this. I was hoping to
implement a delay instead of having to kill getty. I
14 matches
Mail list logo
