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
On Sun, 21 May 2023 15:32:14 +0530
Virendra Negi wrote:
> 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
Am So., 21. Mai 2023 um 18:26 Uhr schrieb Stephen Hemminger
:
> Syslog was never really intended for large size messages. It is not Windows
> event log.
> If you are sending large complex things then using dbus to communicate
> directly
> is a better option.
dbus is not a suitable protocol for
Ok, I think I get a sense of who is doing what which results in the Large
Message getting Split as per my understanding it's *LINE_MAX* value in the
`journalctl` conf that causes the Large message to get split.
The default value is 48K and compared to the size of the split message and
it comes
> Syslog was never really intended for large size messages. It is not
Windows event log.
> If you are sending large complex things then using dbus to communicate
directly
> is a better option.
Now I'm bit prepexled uptil now I was under the impression that the large
message is getting split as a
