On Mon, Aug 4, 2014 at 9:05 PM, Enrico Scholz <
enrico.sch...@sigma-chemnitz.de> wrote:
> Sujith H <sujith.h-re5jqeeqqe8avxtiumw...@public.gmane.org> writes:
>
> > If hostname is not added to /etc/hosts file then rpcinfo command fails
> > when hostname is passed as argument.
> > ...
> > root@mx6q:~# rpcinfo -s mx6q
> > rpcinfo: can't contact rpcbind: RPC: (unknown error code)
>
> Is this really a common/valid use case? 'rpcinfo' is a debug tool and
> when you want information about the local host, you can execute
>
> # rpcinfo -s localhost
>
> IMHO, when using network related functionality, you have to setup
> networking. This means:
>
> - setup the hostname; using ${MACHINE} is ambiguous with more than one
> device and the string can contain chars forbidden by DNS ('_')
>
> - setup name resolving; this can be done by ordinary DNS, (unambiguous)
> /etc/hosts, mDNS
>
>
> When DNS mapping of ${MACHINE} (or better `hostname`) without working
> DNS is really required, 'systemd' contains 'libnss_myhostname.so' (which
> is to be registered in /etc/nsswitch) which returns '127.0.0.2' as a
> fallback.
>
>
Is it ok to read from /etc/hostname and then have that in the /etc/hosts
file, rather than using ${MACHINE}?
>
> Enrico
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
--
സുജിത് ഹരിദാസന്
Bangalore
<Project>Contributor to KDE project
http://fci.wikia.com/wiki/Anti-DRM-Campaign
<Blog> http://sujithh.info
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
