Bug 11715 - syslog() does not include usecs in timestamp
Summary: syslog() does not include usecs in timestamp
Status: SUSPENDED
Alias: None
Product: glibc
Classification: Unclassified
Component: libc (show other bugs)
Version: 2.3.4
: P3 enhancement
Target Milestone: ---
Assignee: Ulrich Drepper
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-17 20:46 UTC by Naresh
Modified: 2015-01-13 07:57 UTC (History)
4 users (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:
fweimer: security-


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Naresh 2010-06-17 20:46:01 UTC
The syslog() function does not include usecs(micro seconds) in the timestamp.

Time stamp is included in the syslog message header.
syslog-ng uses this timestamp as source timestamp to log the message.
syslog-ng supports microseconds, but libc function syslog() doesnot include 
microseconds.
Comment 1 Ulrich Drepper 2010-06-19 18:40:39 UTC
The format used is the one which has been always used.  This means consumers
expect this format and might break if the additional information is added.  I
suspend this until someone with enough interest comes up with a scheme which
doesn't break anything.
Comment 2 Vincenzo Romano 2015-01-13 07:57:35 UTC
As per RFC5424, chapter 6, the field TIME-SECFRAC is optional.
And the meaning of "optional" is explained in RFC2119 chapter 5.
This basically means that:
1. it's OK if this field is missing
2. it's OK if this field is present
In either case, no piece of software should break upon submitting, delivering or receiving such a message.

The ticket issuer should discuss with "whoever in charge"(tm) whether this is a desirable enhancement or not.