I am currently in a twisted maze of service level agreements and similar, pushed around by graph-viewers... It would be extremely nice to have a timestamp (time_t is good enough) on the notify lines in the nsd log, when nsd is logging to a file and not through syslog. -- M?ns Nilsson Systems Specialist +46 70 681 7204 cell KTHNOC +46 8 790 6518 office MN1334-RIPE -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 186 bytes Desc: not available URL: <http://lists.nlnetlabs.nl/pipermail/nsd-users/attachments/20050913/80d0ea38/attachment.bin>
[On 13 Sep, @11:15, M?ns Nilsson wrote in "Feature request. ..."]> I am currently in a twisted maze of service level agreements and similar, > pushed around by graph-viewers... > > It would be extremely nice to have a timestamp (time_t is good enough) on > the notify lines in the nsd log, when nsd is logging to a file and not > through syslog.ack, sounds like a reasonable request to me, -- grtz, - Miek http://www.miek.nl http://www.nlnetlabs.nl PGP Key ID: 0xB18453A1 fingerprint: 002B B079 0DDA 7D44 2B5C CAB0 C3B7 F943 B184 53A1 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: <http://lists.nlnetlabs.nl/pipermail/nsd-users/attachments/20050913/87b72fe0/attachment.bin>
> It would be extremely nice to have a timestamp (time_t is good enough) on > the notify lines in the nsd log, when nsd is logging to a file and not > through syslog.This would be very useful. Syslog does not log either the year or the timezone, making correlation between different systems a bit difficult. Nick
On 9/13/05, M?ns Nilsson <mansaxel at sunet.se> wrote:> It would be extremely nice to have a timestamp (time_t is good enough) on > the notify lines in the nsd log, when nsd is logging to a file and not > through syslog.Can it log to a pipe (without patching?) You could use DJB multilog