Brandon Vincent writes:
> On Mar 15, 2016 3:44 AM, "Loris Bennett"
> wrote:
>> What other files could have an influence on what 'hostname' returns?
>
> Could you post the output of
>
> getent hosts [hostname] and getent hosts [ip] for both systems?
>
> Also please post the hosts line from nsswit
Brandon Vincent writes:
> On Mar 16, 2016 7:56 AM, "Loris Bennett"
> wrote:
>>
>> Brandon Vincent writes:
>>
>> > On Mar 15, 2016 3:44 AM, "Loris Bennett"
>> > wrote:
>> >> What other files could have an influence on what 'hostname' returns?
>> >
>> > Could you post the output of
>> >
>> > get
I haven't been following this email chain, but I see that you asked:
Is there any way to tell that the hostname has been set via
hostname some.random.address
rather via some init script reading /etc/sysconfig/network?
To satisfy my own curiosity I looked on an SL6.7 computer for how
On Mar 15, 2016 3:44 AM, "Loris Bennett" wrote:
> What other files could have an influence on what 'hostname' returns?
Could you post the output of
getent hosts [hostname] and getent hosts [ip] for both systems?
Also please post the hosts line from nsswitch.conf from both machines.
Brandon Vin
On Wed, Mar 16, 2016 at 1:53 PM, Loris Bennett
wrote:
> Tom H writes:
>> On Tue, Mar 15, 2016 at 1:42 PM, Nico Kadel-Garcia wrote:
>>> On Tue, Mar 15, 2016 at 8:32 AM, Nico Kadel-Garcia wrote:
>>>
The problem is that the $HOSTNAME for the system isn't published in
DNS, nor is it the f
On Tue, Mar 15, 2016 at 1:42 PM, Nico Kadel-Garcia wrote:
> On Tue, Mar 15, 2016 at 8:32 AM, Nico Kadel-Garcia wrote:
>
>> The problem is that the $HOSTNAME for the system isn't published in
>> DNS, nor is it the first hostname for a line in /etc/hosts, so the
>> "hostname --fqdn" is not finding
Tom H writes:
> On Tue, Mar 15, 2016 at 1:42 PM, Nico Kadel-Garcia wrote:
>> On Tue, Mar 15, 2016 at 8:32 AM, Nico Kadel-Garcia wrote:
>>
>>> The problem is that the $HOSTNAME for the system isn't published in
>>> DNS, nor is it the first hostname for a line in /etc/hosts, so the
>>> "hostname
On Mar 16, 2016 7:56 AM, "Loris Bennett" wrote:
>
> Brandon Vincent writes:
>
> > On Mar 15, 2016 3:44 AM, "Loris Bennett"
> > wrote:
> >> What other files could have an influence on what 'hostname' returns?
> >
> > Could you post the output of
> >
> > getent hosts [hostname] and getent hosts [i
Tom H writes:
> On Wed, Mar 16, 2016 at 1:53 PM, Loris Bennett
> wrote:
>> Tom H writes:
>>> On Tue, Mar 15, 2016 at 1:42 PM, Nico Kadel-Garcia wrote:
On Tue, Mar 15, 2016 at 8:32 AM, Nico Kadel-Garcia
wrote:
> The problem is that the $HOSTNAME for the system isn't publish
On Fri, Mar 18, 2016 at 1:22 AM, Steven J. Yellin
wrote:
>
> To satisfy my own curiosity I looked on an SL6.7 computer for how
> hostname gets set.
>
> In /etc/init.d/network, which brings networking up and down, are lines
>
> cd /etc/sysconfig/network-scripts
> . ./network-functions
> and calls t
Hi Andrew,
Andrew C Aitchison
writes:
> On Tue, 15 Mar 2016, Loris Bennett wrote:
>
>> Hi,
>>
>> I'm using ansible to set up two servers and have run into the problem
>> that on one server 'hostname' returns the just the name of the machine,
>> but on the other I get the FQDN:
>>
>> # hostname -
On Tue, 15 Mar 2016, Loris Bennett wrote:
Hi,
I'm using ansible to set up two servers and have run into the problem
that on one server 'hostname' returns the just the name of the machine,
but on the other I get the FQDN:
# hostname -s; hostname -d; hostname -f; hostname
tadmin01
test.cluster
t
Hi Nico,
Nico Kadel-Garcia
writes:
[snip (27 lines)]
> "system-config-network-tui" works pretty well if installed.
I've had a look at the settings with this, and the setting are as I
expect.
> The problem is that the $HOSTNAME for the system isn't published in
> DNS, nor is it the first hostn
Hi Paddy,
Paddy Doyle writes:
> Hi Loris,
>
> On Tue, Mar 15, 2016 at 11:43:55AM +0100, Loris Bennett wrote:
>
>> Hi,
>>
>> I'm using ansible to set up two servers and have run into the problem
>> that on one server 'hostname' returns the just the name of the machine,
>> but on the other I get
On Tue, Mar 15, 2016 at 8:32 AM, Nico Kadel-Garcia wrote:
> The problem is that the $HOSTNAME for the system isn't published in
> DNS, nor is it the first hostname for a line in /etc/hosts, so the
> "hostname --fqdn" is not finding it associated with your IP addresses.
> The usual approach for po
Hi Loris,
On Tue, Mar 15, 2016 at 11:43:55AM +0100, Loris Bennett wrote:
> Hi,
>
> I'm using ansible to set up two servers and have run into the problem
> that on one server 'hostname' returns the just the name of the machine,
> but on the other I get the FQDN:
>
> # hostname -s; hostname -d; h
On Tue, Mar 15, 2016 at 7:04 AM, Loris Bennett
wrote:
> Hi Benjamin,
>
> Benjamin Lefoul writes:
>
>> Hi Loris,
>>
>> On SL7, I believe hostnames are best set declaratively in the file
>> /etc/hostname (as has been the case for long on other distros). I
>> suspect the preferred imperative way to
Hi Benjamin,
Benjamin Lefoul writes:
> Hi Loris,
>
> On SL7, I believe hostnames are best set declaratively in the file
> /etc/hostname (as has been the case for long on other distros). I
> suspect the preferred imperative way to set hostname is with
> "hostnamectl set-hostname" (check the man
l
nWISE AB
From: owner-scientific-linux-us...@listserv.fnal.gov
on behalf of Loris Bennett
Sent: 15 March 2016 11:43
To: scientific-linux-us...@fnal.gov
Subject: Setting hostname
Hi,
I'm using ansible to set up two servers and have run into the
Hi,
I'm using ansible to set up two servers and have run into the problem
that on one server 'hostname' returns the just the name of the machine,
but on the other I get the FQDN:
# hostname -s; hostname -d; hostname -f; hostname
tadmin01
test.cluster
tadmin01.test.cluster
tadmin01
# hostname -s
Final update,
after a very productive exchange via the redhat bug tracking system, it
turned out my BIOS was causing the problem. Flashed the latest version an
d
voila it works like a charm. (Samsung Q45 BIOS ST7 to version ST11)
Before that I could get it to boot with kernel options pci=nomsi acpi
Update:
I just tried booting the 5.3 Live CD, which also fails at the same point,
so
I assume it's a general hardware/driver issue.
SL 5.4
Kernel 2.6.18-164.2.1.e15
x86_64
Samsung Q45
Hello!
I've managed to install SL 5.4 from DVDs but cannot boot into the system. The
boot sequence freezes when reaching or shortly after "setting hostname [OK]".
I've tried booting with nousb set and rhgb disabled, to
23 matches
Mail list logo
