luding 480 octets has, among other things, to do with
>difficult delivery problems in a broken network."
>
> -Original Message-
> From: systemd-devel On
> Behalf Of Virendra Negi
> Sent: Sunday, May 21, 2023 12:02 PM
> To: systemd-devel@lists.freedesktop.org
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
om/systemd/systemd/blob/main/src/journal/journald-stream.c#L498
I
don't think there exists anything like it. Still want to check if there is
anything possible?
Thanks
On Mon, May 22, 2023 at 4:44 AM Virendra Negi <
virendra.n...@sugarboxnetworks.com> wrote:
> > Syslog was never rea
> 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
> .. End
>
*Start ... End* suppose to be a single line but because it reach the upper
limit of 48K it was broken. Now how can I assemble them?
Thanks
On Mon, May 22, 2023 at 2:01 PM Lennart Poettering
wrote:
> On Mo, 22.05.23 09:31, Virendra Negi (virendra.n...@sugarboxnetworks.com
Thanks, Lennart.
On Mon, May 22, 2023 at 4:28 PM Lennart Poettering
wrote:
> On Mo, 22.05.23 15:58, Virendra Negi (virendra.n...@sugarboxnetworks.com)
> wrote:
>
> > I'm not sure how Systemd was handling this, but my assumption is that
> > systemd redirects STDOUT ,
May be it helps that these are not often that these large log messages
would be sent.
On Sat, May 27, 2023 at 10:26 PM Cristian Rodríguez <
crrodrig...@opensuse.org> wrote:
>
>
> On Thu, May 25, 2023 at 10:44 PM Virendra Negi <
> virendra.n...@sugarboxnetworks.co
