From: Chris Lieb <chris.lieb@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Logwatch not resolving hostname
Date: Fri, 27 Feb 2009 10:14:49 -0600 [thread overview]
Message-ID: <49A81179.2040700@gmail.com> (raw)
In-Reply-To: <49A807F4.8070104@gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Chris Lieb wrote:
> Chris Lieb wrote:
>> 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
>
> I believe I've found the problem! There is a hash called %swordsmen
> that defines a pair of 'high => 10'. It appears that a function is
> calling getInt, which uses %wordsToInts to process hostname, turning my
> hostname of 'high' into '10'.
>
> I'm going to play around with it some more to see if this is the case.
It ends up that was the issue. I have opened bug 260524 on Gentoo
Bugzilla that includes a patch and a -r1 ebuild for 7.3.6, which went
stable yesterday.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iQEcBAEBAgAGBQJJqBF5AAoJEJWxx7fgsD+CY1AIAKFqDK3e49MuiLlcgJYMHmRU
Mm09ijk6JECqGjLzfyFbnlhIItKX5njS/NGu8Ki9mr53LTc3A0M08MGEbeg2TJl6
XZPzR/DM/5x9EWZn6uIVxY3mLo/G4xTj1EOWH/aGpQN7uDDQFNjq27gnkfs3V2VB
gNLxN1lylSep6u0knIcvdtt90xHyk3TLwgNORn2KgDSEJPmRIz9hpglrNIHganyQ
ihl2t1SVTitdyKNyhaj5NcYy9BMJDRjyhgZ+FPBEkW27ekaJUQhP/16VlftQVLjk
62Z0Dz7J7Je0jLh2ldLi1+p/iyNxyKH8IXstmDsrwiMU39mjmtDJn3R8zcKBV6A=
=Rq6i
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2009-02-27 16:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 15:22 [gentoo-user] Logwatch not resolving hostname Chris Lieb
2009-02-27 15:34 ` [gentoo-user] " Chris Lieb
2009-02-27 16:14 ` Chris Lieb [this message]
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=49A81179.2040700@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