samba - Jun 2014 - bug in samba?

So, comming back on the never ending resolving issues. 
?
Now im not a coder, but when we look at this example..
?
To draw another parallel, you seem to want the output of the command hostname
--fqdn (which depends on the resolver), while others want hostname .

getfqdn seems to return a different result than gethostname if the hostname of
the machine is an alias.

For example if I have this in /etc/hosts and with some python testing. 
127.0.0.1 localhost localhost.localdomain localhost2 localhost2.localdomain2
mypersonaldomainname.tld
?
python -c 'import socket; print socket.getfqdn()'
?
gives localhost.localdomain
?
python -c 'import socket; print socket.gethostname()'
?
gives mypersonaldomainname.tld
?
?
so how does samba get the hostname?? 
?
?
?

Louis
?

?

On 06/25/14 09:52, L.P.H. van Belle wrote:
> So, comming back on the never ending resolving issues.
>   
> Now im not a coder, but when we look at this example..
>   
> To draw another parallel, you seem to want the output of the command
hostname --fqdn (which depends on the resolver), while others want hostname .
>
> getfqdn seems to return a different result than gethostname if the hostname
of the machine is an alias.
>
> For example if I have this in /etc/hosts and with some python testing.
> 127.0.0.1 localhost localhost.localdomain localhost2
localhost2.localdomain2 mypersonaldomainname.tld
>   
> python -c 'import socket; print socket.getfqdn()'
>   
> gives localhost.localdomain
>   
> python -c 'import socket; print socket.gethostname()'
>   
> gives mypersonaldomainname.tld
>   
>   
> so how does samba get the hostname?
Seems to be an underlying  python issue: http://bugs.python.org/issue5004

Apparently socket.getfqdn() is not even give the same result in 
consecutive calls.

good luck ;-)

cheers
-henrik