| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Chris Lieb wrote: |
| 5 |
> Chris Lieb wrote: |
| 6 |
>> I have recently setup logwatch-7.3.2 on a few of my machines along with |
| 7 |
>> sendmail. For all but one of the machines, I get emails that have the |
| 8 |
>> hostname in the subject line (Logwatch for capitol (Linux)) as well as |
| 9 |
>> on the line that reads 'Logfiles for Host' (Logfiles for Host: capitol). |
| 10 |
> |
| 11 |
>> However, on one machine, the hostname is not resolved correctly. The |
| 12 |
>> email has the subject line 'Logwatch for 10 (Linux)' and in the body of |
| 13 |
>> the email has 'Logfiles for Host: 10'. The IP address of this machine |
| 14 |
>> is 10.192.202.xxx, and the hostname is high. |
| 15 |
> |
| 16 |
>> When I do a `hostname -va` on high, I get: |
| 17 |
>> gethostname()=`high' |
| 18 |
>> Resolving `high' ... |
| 19 |
>> Result: h_name=`high.opcdir.intranet' |
| 20 |
>> Result: h_aliases=`high' |
| 21 |
>> Result: h_aliases=`localhost' |
| 22 |
>> Result: h_addr_list=`127.0.0.1' |
| 23 |
>> high localhost |
| 24 |
>> When I run the same command on congress, which has a working logwatch, I |
| 25 |
>> get: |
| 26 |
>> gethostname()=`congress' |
| 27 |
>> Resolving `congress' ... |
| 28 |
>> Result: h_name=`congress.opcdir.intranet' |
| 29 |
>> Result: h_aliases=`congress' |
| 30 |
>> Result: h_aliases=`localhost' |
| 31 |
>> Result: h_addr_list=`127.0.0.1' |
| 32 |
>> congress localhost |
| 33 |
>> This seems to me to eliminate the possibility of a misconfigured |
| 34 |
>> hostname on high. |
| 35 |
> |
| 36 |
>> Does anyone have an idea as to what is causing logwatch to not resolve |
| 37 |
>> the hostname correctly? |
| 38 |
> |
| 39 |
>> Thanks, |
| 40 |
>> Chris Lieb |
| 41 |
> |
| 42 |
> I believe I've found the problem! There is a hash called %swordsmen |
| 43 |
> that defines a pair of 'high => 10'. It appears that a function is |
| 44 |
> calling getInt, which uses %wordsToInts to process hostname, turning my |
| 45 |
> hostname of 'high' into '10'. |
| 46 |
> |
| 47 |
> I'm going to play around with it some more to see if this is the case. |
| 48 |
|
| 49 |
It ends up that was the issue. I have opened bug 260524 on Gentoo |
| 50 |
Bugzilla that includes a patch and a -r1 ebuild for 7.3.6, which went |
| 51 |
stable yesterday. |
| 52 |
-----BEGIN PGP SIGNATURE----- |
| 53 |
Version: GnuPG v1.4.9 (MingW32) |
| 54 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
| 55 |
|
| 56 |
iQEcBAEBAgAGBQJJqBF5AAoJEJWxx7fgsD+CY1AIAKFqDK3e49MuiLlcgJYMHmRU |
| 57 |
Mm09ijk6JECqGjLzfyFbnlhIItKX5njS/NGu8Ki9mr53LTc3A0M08MGEbeg2TJl6 |
| 58 |
XZPzR/DM/5x9EWZn6uIVxY3mLo/G4xTj1EOWH/aGpQN7uDDQFNjq27gnkfs3V2VB |
| 59 |
gNLxN1lylSep6u0knIcvdtt90xHyk3TLwgNORn2KgDSEJPmRIz9hpglrNIHganyQ |
| 60 |
ihl2t1SVTitdyKNyhaj5NcYy9BMJDRjyhgZ+FPBEkW27ekaJUQhP/16VlftQVLjk |
| 61 |
62Z0Dz7J7Je0jLh2ldLi1+p/iyNxyKH8IXstmDsrwiMU39mjmtDJn3R8zcKBV6A= |
| 62 |
=Rq6i |
| 63 |
-----END PGP SIGNATURE----- |
Archives