public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris Lieb <chris.lieb@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Logwatch not resolving hostname
Date: Wed, 25 Feb 2009 09:22:35 -0600	[thread overview]
Message-ID: <49A5623B.8090904@gmail.com> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I have recently setup logwatch-7.3.2 on a few of my machines along with
sendmail.  For all but one of the machines, I get emails that have the
hostname in the subject line (Logwatch for capitol (Linux)) as well as
on the line that reads 'Logfiles for Host' (Logfiles for Host: capitol).

However, on one machine, the hostname is not resolved correctly.  The
email has the subject line 'Logwatch for 10 (Linux)' and in the body of
the email has 'Logfiles for Host: 10'.  The IP address of this machine
is 10.192.202.xxx, and the hostname is high.

When I do a `hostname -va` on high, I get:
  gethostname()=`high'
  Resolving `high' ...
  Result: h_name=`high.opcdir.intranet'
  Result: h_aliases=`high'
  Result: h_aliases=`localhost'
  Result: h_addr_list=`127.0.0.1'
  high localhost
When I run the same command on congress, which has a working logwatch, I
get:
  gethostname()=`congress'
  Resolving `congress' ...
  Result: h_name=`congress.opcdir.intranet'
  Result: h_aliases=`congress'
  Result: h_aliases=`localhost'
  Result: h_addr_list=`127.0.0.1'
  congress localhost
This seems to me to eliminate the possibility of a misconfigured
hostname on high.

Does anyone have an idea as to what is causing logwatch to not resolve
the hostname correctly?

Thanks,
Chris Lieb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQEcBAEBAgAGBQJJpWI7AAoJEJWxx7fgsD+Cq+8H/RwGltiY8fvbAfee3/e/jYG9
WyOm187M6LZBQ3hWJ2Q558hQUNr86CqfaLBwPaOeBK8KEv1WvhAS5iyQo/4FNU77
X7y+EwEpF4X1mYV0MNm+zLmvd/XqEeSCxNe96N6bubyXxSh+/uAR4Seqd4TtwjKH
aOVqvN94skUJY4MVgLHHrjbDVwNkv6TqVTIKDRquj3qx21TzKsMj3VrxlGUinvIW
/nXs0hI4SYWOXIB+t29z/P80KPSozJW9OW2GuEJIeph91eKoc9H8nfcFLE3I1k3x
dMAdxEtF7fPUB2KmIizRAoOauKYHHkPqPbxvUDqh8T3JABfzYu+cG4v7xuRfok4=
=Y0K4
-----END PGP SIGNATURE-----



             reply	other threads:[~2009-02-25 15:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-25 15:22 Chris Lieb [this message]
2009-02-27 15:34 ` [gentoo-user] Re: Logwatch not resolving hostname Chris Lieb
2009-02-27 16:14   ` Chris Lieb

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49A5623B.8090904@gmail.com \
    --to=chris.lieb@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox