Re: [Ganglia-developers] Problems caused by using gethostbyXXX.

2003-03-26 Thread Jason A. Smith
Remember, this all started from noticing that a network configuration that might even be common on Solaris can cause a mixture of short and long hostnames when gmond does the name lookup from the IP in the multicast data. If your primary query node goes down or is unreachable for some other reason

Re: [Ganglia-developers] Problems caused by using gethostbyXXX.

2003-03-26 Thread Leif Nixon
"Jason A. Smith" <[EMAIL PROTECTED]> writes: > As long as the hostnames that ganglia gets from the IPs are consistently > in the fqdn format then it would be better than the current situation > which results in a mixture of short and full names. That isn't possible, in the general case. FQDN is a

Re: [Ganglia-developers] Problems caused by using gethostbyXXX.

2003-03-25 Thread Jason A. Smith
That solution would be fine also, I didn't mean to imply that ganglia should be using bind, just meant to offer it as one possible solution. As long as the hostnames that ganglia gets from the IPs are consistently in the fqdn format then it would be better than the current situation which results

Re: [Ganglia-developers] Problems caused by using gethostbyXXX.

2003-03-20 Thread Steven Wagner
An amazing variety of things are keyed off an /etc/hosts entry in Solaris (including network interface configuration, if memory serves). This man speaks the truth. However, I put it to you, world, that if this has only popped up on Sun boxes, a better solution might be to quietly change solar

[Ganglia-developers] Problems caused by using gethostbyXXX.

2003-03-20 Thread Jason A. Smith
I noticed a potential problem that results from the use of the gethostbyXXX functions. We have a small group of Sun file servers that we want to monitor with ganglia. The problem originates from having an /etc/hosts file that includes an entry for your local host that has both the short and fqdn