Wireshark suggests that the message is being sent and received. However, RFC3164 suggests that there's no hard, normative standard for sending events over TCP: some applications end events with LF, some with CRLF, and some use byte-counting. Sys::Syslog likes LF+NUL and gives you a way to suppress the null, but the option to suppress the LF doesn't work; I've raised a ticket for that and another for the RFC-violating date format. All in all, with no standards and without the ability to suppress the LF experimentally, it's not surprising that the syslog collectors we've tried don't really like the events that Sys::Syslog emits. :-(
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|