Hi
In RFC3164 we have (by error) defined the TAG as part of the MSG part.
In syslog-sign, we correct is by saying "the TAG should be .."
However, in rfc3164 the "pid" part isn't part of the TAG (see below). But
for the same (API) reasons as described in syslog-sign, it should be part of
the header. (when it is used).
Can/Should we define this in -sign. Or better, define it as part of "TAG".
Example, should we define the message below as "1", "2" or "3".
<12> ${date} ${host} ntpd[1234]: set the time
1) |---header----|-------msg---------------|
2) |-----header---------|---------msg------|
3) |-----header---------------|---msg------|
rfc3164 say: 1
-sign(04) says 2
I say: 3
Only no 3 is handy for implementing!
In several discussion, I think "3" meand, but "2" is now described.
Please correct me if I'm wrong
--ALbert
sent mail to [EMAIL PROTECTED], to address me personal.
sent mail to [EMAIL PROTECTED], to address me for businesses
