Subject: Re: RFC: enhancement to syslogd - always printing local time
To: Pavel Cahyna <pavel.cahyna@st.mff.cuni.cz>
From: Luke Mewburn <lukem@NetBSD.org>
List: tech-userlevel
Date: 01/15/2006 23:51:45
--de1H0RjRxOSdb4we
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Jan 09, 2006 at 11:09:33PM +0100, Pavel Cahyna wrote:
  | syslogd has currently an undocumented feature - if it does not recognize
  | the timestamp field in the received message, it generates it, based on =
the
  | local time.
  |=20
  | I would like to optionally generate timestamp field for all messages
  | received from network, regardless of validity of the timestamp field.
  |=20
  | I expect that such a feature can be generally useful, especially for the
  | first reason. (Devices that don't keep time properly must be quite comm=
on.)
  | So here is a patch which implements a -T option, causing syslogd to
  | generate a timestamp field for all messages received over the network.
  |=20
  | Is it worth integrating in NetBSD sources?

I like the idea.

--de1H0RjRxOSdb4we
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (NetBSD)

iD8DBQFDykVhpBhtmn8zJHIRAp+9AKDBa796ccq4gR26Mpn0KmU7T0Ar4wCdFrHy
hFXr++wuqwTUWTe227HcDDA=
=8v23
-----END PGP SIGNATURE-----

--de1H0RjRxOSdb4we--