On 05/31/2016 11:27 PM, Ryan Novosielski wrote:
You are most welcome.
So here’s some followup: many of us have had this problem before, and it seems OS-specific. Is there any way to get this more right by default? I see that many/most of my entries in hosts.cfg have CLIENT:<hostname> specified. My server is Solaris 10, my clients are a mixture of things. In theory, a hostname contains no domain suffix. So you should never have a FQDN in your hosts.cfg
Stef
On Wed, Jun 1, 2016 at 5:11 PM Stef Coene <stef.coene at docum.org> wrote:
On 05/31/2016 11:27 PM, Ryan Novosielski wrote:
So here’s some followup: many of us have had this problem before, and it seems OS-specific. Is there any way to get this more right by default? I see that many/most of my entries in hosts.cfg have CLIENT:<hostname> specified. My server is Solaris 10, my clients are a mixture of things.
In theory, a hostname contains no domain suffix.
Yes, possibly. What the xymon client uses as a "hostname" when it creates
a client message is $MACHINEDOTS, which the output of uname -n. POSIX
defines this as the "network node name" which doesn't really say if it's
the FQDN or the shortname.
So you should never have a FQDN in your hosts.cfg
So what if you have www.internal.example.com <http://www.in.telstra.com> and www.example.com? It seems to me that the primary attribute for a hostname is for it to be unique. On the Internet, that generally means FQDN.
J
Hi,
I think, the default is to use FQDN. It is defined in xymonserver.cfg:
General settings
FQDN="TRUE" # Use fully-qualified hostnames internally. Keep it TRUE unless you know better.
So you should never have a FQDN in your hosts.cfgSo what if you have www.internal.example.com <http://www.in.telstra.com> and www.example.com <http://www.example.com>? It seems to me that the primary attribute for a hostname is for it to be unique. On the Internet, that generally means FQDN.
Regards, Dirk
Absolutely true. Also from the Xymon message format documentation:
http://xymon.sourceforge.net/xymon/help/manpages/man1/xymon.1.html
"XYMON MESSAGE SYNTAX
This section lists the most commonly used messages in the Xymon protocol.
Each message must begin with one of the Xymon commands. Where a HOSTNAME is specified, it must have any dots in the hostname changed to commas if the Xymon FQDN setting is enabled (which is the default). So the host "www.foo.com", for example, would report as "www,foo,com”." —
I took a look at the clientlog test on my equipment, under the first [collector] stanza, for all of my equipment: it is FQDN on almost all of my Linux machines, and it is hostname-only on almost all of my Solaris machines.
On Jun 1, 2016, at 5:29 AM, Dirk Kastens <dirk.kastens at uni-osnabrueck.de> wrote:
Hi,
I think, the default is to use FQDN. It is defined in xymonserver.cfg:
General settings
FQDN="TRUE" # Use fully-qualified hostnames internally. Keep it TRUE unless you know better.
So you should never have a FQDN in your hosts.cfg
So what if you have www.internal.example.com <http://www.in.telstra.com> and www.example.com <http://www.example.com>? It seems to me that the primary attribute for a hostname is for it to be unique. On the Internet, that generally means FQDN.
--
|| \\UTGERS, |---------------------------*O*--------------------------- ||_// the State | Ryan Novosielski - novosirj at rutgers.edu || \\ University | Sr. Technologist - 973/972.0922 (2x0922) ~*~ RBHS Campus || \\ of NJ | Office of Advanced Research Computing - MSB C630, Newark `'
On 5/31/2016 11:11 PM, Stef Coene wrote:
On 05/31/2016 11:27 PM, Ryan Novosielski wrote:
You are most welcome.
So here’s some followup: many of us have had this problem before, and it seems OS-specific. Is there any way to get this more right by default? I see that many/most of my entries in hosts.cfg have CLIENT:<hostname> specified. My server is Solaris 10, my clients are a mixture of things.
In theory, a hostname contains no domain suffix. So you should never have a FQDN in your hosts.cfg
{bangs head on desk} This approach is so 1998 . . .
Moving from Big Brother to Xymon was so liberating because we finally got consistent "fully qualified domainn name" (FQDN) support. There is no reason not to use FQDN in your hosts.cfg. Use them. It is silly not to.
All of the hosts in my Xymon are defined with FQDN. But there are several which also have "CLIENT:" tags defined with their "short" name. These are generally:
- Hosts running scripts from our BB days before we had FQDN support
- Windows hosts whose admins don't know how to configure the client
- Editors who blindly copy some other line from hosts.cfg and assume they must have a CLIENT: tag
IMHO, anyone using truncated host names in their hosts.cfg should have to justify each of those entries in writing. FQDNs work. Make the world a better place; use them.
-- Do things because you should, not just because you can.
John Thurston 907-465-8591 John.Thurston at alaska.gov Enterprise Technology Services Department of Administration State of Alaska
participants (5)
-
dirk.kastens＠uni-osnabrueck.de
-
jlaidman＠rebel-it.com.au
-
john.thurston＠alaska.gov
-
novosirj＠rutgers.edu
-
stef.coene＠docum.org