[systemd-devel] [EXT] Splitting large message written to stdout, explanation?

Virendra Negi virendra.negi at sugarboxnetworks.com
Fri May 26 02:44:00 UTC 2023


@Windl but the logs are sent to rsyslog is over unix socket.

On Thu, May 25, 2023 at 12:22 PM Windl, Ulrich <u.windl at ukr.de> wrote:

> Maybe syslog is just the wrong thing for your purpose:
> RFC 5424 states: "The reason syslog transport receivers need only support
> receiving up
>    to and including 480 octets has, among other things, to do with
>    difficult delivery problems in a broken network."
>
> -----Original Message-----
> From: systemd-devel <systemd-devel-bounces at lists.freedesktop.org> On
> Behalf Of Virendra Negi
> Sent: Sunday, May 21, 2023 12:02 PM
> To: systemd-devel at lists.freedesktop.org
> Subject: [EXT] [systemd-devel] Splitting large message written to stdout,
> explanation?
>
> It's been over a week I have been chasing this
> https://github.com/rsyslog/rsyslog/issues/5137
>
> I was unsure how to ensure that the systemd (since I was getting nowhere
> with rsyslog)  split the message instead of the application program doing
> this.
>
> Apparently, today I just removed the following section from the
> `target.service` file
>
> StandardOutput=syslog
> StandardError=syslog
> SyslogIdentifier=sbagent
> And set the MaxMessageSize to 64K and what I saw was the 1.5MB long
> message that was truncating earlier went through this time without
> truncation and a split happened the way I wanted it to be.
>
> I'm unsure what caused it hence for the sake of understanding it. I'm
> writing this. Can someone put some light on it as to why this happened now
> and not earlier.
>
>
> Thanks
>
>
>
>  <
> https://sugarbox.sgp1.cdn.digitaloceanspaces.com/logo-signature-small.jpg>
>
>  <https://www.facebook.com/SugarBoxNetworks/>   <
> https://www.instagram.com/sugarboxnetworks/>   <
> https://in.linkedin.com/company/margo-networks-pvt.-ltd.>
>
>
> Disclaimer: This e-mail and any documents, files, or previous e-mail
> messages appended or attached to it may contain confidential and/or
> privileged information. If you are not the intended recipient (or have
> received this email in error) please notify the sender immediately and
> delete this e-mail. Any unauthorized copying, disclosure or distribution of
> the material in this email is strictly prohibited & unlawful. The recipient
> acknowledges that Margo Networks Private Limited (SugarBox) may be unable
> to exercise control or ensure or guarantee the integrity of the text of the
> email message and the text is not warranted as to completeness and
> accuracy. Before opening and accessing the attachment, if any, please check
> and scan for virus
>
>

-- 

 <https://www.facebook.com/SugarBoxNetworks/>  
<https://www.instagram.com/sugarboxnetworks/>  
<https://in.linkedin.com/company/margo-networks-pvt.-ltd.>




-- 
**Disclaimer*: This e-mail and any documents, files, or previous e-mail 
messages appended or attached to it may contain confidential and/or 
privileged information. If you are not the intended recipient (or have 
received this email in error) please notify the sender immediately and 
delete this e-mail. Any unauthorized copying, disclosure or distribution of 
the material in this email is strictly prohibited & unlawful. The recipient 
acknowledges that Margo Networks Private Limited (SugarBox) may be unable 
to exercise control or ensure or guarantee the integrity of the text of the 
email message and the text is not warranted as to completeness and 
accuracy. Before opening and accessing the attachment, if any, please check 
and scan for virus*




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/systemd-devel/attachments/20230526/123e4a6a/attachment.htm>


More information about the systemd-devel mailing list