At 12:07 PM 2/22/01 +0100, Alfonso De Gregorio wrote:
>If you feel this notation ambiguous, one of the examples could be changed
>to have in the TIMESTAMP a day of the month less than 10.
Hi Alfonso,
Good idea. I've made the following change to Example 2:
====
Example 2
<14>Use the BFG!
While this is a valid message, it has extraordinarily little useful
information. It does not contain a timestamp or any indication of
the source of the message. Since it is a user-generated message,
it is consistent that it is not associated with a process and may
therefor not have a TAG. If this message is stored on paper or disk,
subsequent review of the message will not yield anything of value.
This example is obviously an original message from a device. A relay
MUST make changes to the message as described in Section 4.2.2 before
forwarding it. The resulting relayed message is shown below.
<14>Feb 5 17:32:18 10.0.0.99 Use the BFG!
In this relayed message, a TIMESTAMP has been added along with a
HOSTNAME in the MSG part. Subsequent relays will not make any further
changes to this message. It should be noted in this example that the
day of the month is less than 10. Since single digits (5 in this case)
are preceded by a space in the TIMESTAMP format, there are two spaces
following the month in the TIMESTAMP before the day of the month.
Also, the relay appears to have no knowledge of the host name of the
device sending the message so it has inserted the IP address of the
device into the HOSTNAME field.
===
Please comment on this and I'll submit it as syslog-syslog-06.
Thanks,
Chris
