[Logcheck-users] hostname problem

[Jamie L. Penman-Smithson]

--=-CazjXlVamegDy0G+fcPo
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Tue, 2005-05-31 at 20:19 +0100, David Nicholls wrote:
> I'm using logcheck 1.2.39 on Debian Sarge.
>=20
> On the emails I am getting from logcheck, some of the servers are not
> correctly reporting their hostnames. There is no obvious difference in
> the configuration of the servers that report the correct hostname and
> those that don't.
>=20
> I took a looksee at the /usr/sbin/logcheck code and see that the
> relevant section is:
<snip>

This is a known bug in logcheck that was fixed in 1.2.40. The FQDN
option now works as documented.

> Trying commands directly from the command line:
>=20
> hostname gives officefirewall
> hostname --short gives localhost
> hostname --fqdn gives localhost.localdomain

Your short hostname should be officefirewall, your FQDN should be
officefirewall.example.com (replacing example.com with your domain
name). This is configured in /etc/hosts.

If you're running a mail or news server, or sending mail from the system
in question you'll run into trouble if you have localhost.localdomain as
your FQDN, since mail and news servers need a unique FQDN to form a
Message-ID.

Take a look at the Linux NET-3 HOWTO at
http://www.tldp.org/HOWTO/NET3-4-HOWTO-5.html for further info.

> I just wondered if anyone had an idea asto what the problem might be.

-j

--=-CazjXlVamegDy0G+fcPo
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQBCnL200mxM1DK1CAsRAnWUAKCSdH1FiUEUDCa08wN6F1ry+8FNRgCeLlLc
8Er/bvXpxb2olHfg7ILpvRE=
=hnmZ
-----END PGP SIGNATURE-----

--=-CazjXlVamegDy0G+fcPo--