Rainer: > as I am editing -international, I noticed that the TRAILER > specified may be worth looking at. Now that we do not need to > remain backward-compatible, I would opt to have a simple > tailer in the message. It was defined as: > > SYSLOG-MSG = PRI HEADER MSG [TRAILER] > TRAILER = [CR] LF > > While the trailer is not strictly necessary to form the > message, I think it is quite a good sanity check if the > message looks OK.
IMO, if we think the trailer is useful, then it should be required. Making it optional only opens possibilities for misinterpretation. Also, having to deal with two potential variations of trailers is not optimal although I understand the OS differences. Yet another reason to drop it. BTW, previous syslog server implementations (Solaris, for instance) allowed line breaks inside messages. I think there was some discussion about this before, but I am not sure what we concluded. Should we allow them in -protocol? If not, I think we need some other mechanism to handle such messages to ease migration to -protocol. For example, we could extend the scope of message fragmentation for this purpose. Here is Solaris example of what appears in the log file if sending "\n": Oct 11 22:14:15 myhost2 su: Message with line break\nbefore end Now, example when sending "\r\n": Oct 11 22:14:15 myhost2 su: Message with line break^M\nbefore end Thanks, Anton.
