On Wed, Dec 17, 2014 at 08:30:41PM +, Holger Winkelmann [TP] wrote:
> Hi, sorry for delay in reply..
>
> >> Journal carries messages from the initramfs. We cannot send them from
> >> the initramfs, unless we bring up the network then, which we don't want
> >> to do just for this purpose. But t
Hi, sorry for delay in reply..
>> Journal carries messages from the initramfs. We cannot send them from
>> the initramfs, unless we bring up the network then, which we don't want
>> to do just for this purpose. But those messages are stored in /run/log,
>> and then flushed to /var/log, and the upl
>>> >I'm not quite following what you said there but I would actually
>>> >think the former as in "forward it live" is better, ju
>> Journal carries messages from the initramfs. We cannot send them from
>> the initramfs, unless we bring up the network then, which we don't want
>> to do just for th
On Thu, Dec 11, 2014 at 04:43:25PM +, "Jóhann B. Guðmundsson" wrote:
> On 12/11/2014 04:38 PM, Zbigniew Jędrzejewski-Szmek wrote:
> Cant we just tweak those values to suit our needs?
> >You need an address to establish a socket.
No.
> And the socket queue will not
> >be enough if you have cop
On 12/11/2014 04:38 PM, Zbigniew Jędrzejewski-Szmek wrote:
You need an address to establish a socket. And the socket queue will not
be enough if you have copious debug or kernel messages.
Cant we just tweak those values to suit our needs?
JBG
___
sy
On Thu, Dec 11, 2014 at 04:35:24PM +, "Jóhann B. Guðmundsson" wrote:
>
> On 12/11/2014 04:19 PM, Zbigniew Jędrzejewski-Szmek wrote:
> >On Thu, Dec 11, 2014 at 04:09:54PM +, "Jóhann B. Guðmundsson" wrote:
> >>>
> >>>On 12/11/2014 03:31 PM, Zbigniew Jędrzejewski-Szmek wrote:
> >The diff
On 12/11/2014 04:19 PM, Zbigniew Jędrzejewski-Szmek wrote:
On Thu, Dec 11, 2014 at 04:09:54PM +, "Jóhann B. Guðmundsson" wrote:
>
>On 12/11/2014 03:31 PM, Zbigniew Jędrzejewski-Szmek wrote:
> >The difference is in how the logs are accessed: if journald itself does the
jobs,
> >they would
HI,
>> > Or a broadcast address, so no configuration is required.
>>
>> I'd really like to see broadcast delivery I must say.
as mentioned, why not if it can switched off and unicasted to the IP:514
>> > That's rfc5424, right? Then yes.
>>
>> Is that RFC actually widely adopted? I'd stay as c
On Thu, Dec 11, 2014 at 05:18:58PM +0100, Lennart Poettering wrote:
> On Thu, 11.12.14 17:16, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
>
> > > I agree with your findings, and basically thats how the zmq journal
> > > gateway works as
> > > well. And thanks to bring the "wait for net
HI,
>> Would the upload tool learn a new URL for this purpose i.e.
>> syslog://:514 ?
> Or a broadcast address, so no configuration is required.
Hmmm. Admin guys would not really like broadcast here. But anyway would not
argue
much if it can be configured.
>> >> > Initial plan was to implement
On Thu, Dec 11, 2014 at 04:09:54PM +, "Jóhann B. Guðmundsson" wrote:
>
> On 12/11/2014 03:31 PM, Zbigniew Jędrzejewski-Szmek wrote:
> >The difference is in how the logs are accessed: if journald itself does the
> >jobs,
> >they would be forwarded "live". If anything else, the uploader would b
On Thu, 11.12.14 17:16, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
> > I agree with your findings, and basically thats how the zmq journal gateway
> > works as
> > well. And thanks to bring the "wait for network" up here, you would miss
> > important
> > boot log entries here.
> >
On Thu, Dec 11, 2014 at 03:39:56PM +, Holger Winkelmann [TP] wrote:
> Hi,
>
> >> upload sounds a bit of a batch process, but thats just cosmetic wording.
> >>
> >> Having this in systems-journald and extend the forward to syslog config
> >> with the
> >> target
> >> host was our expectation
On 12/11/2014 03:31 PM, Zbigniew Jędrzejewski-Szmek wrote:
The difference is in how the logs are accessed: if journald itself does the
jobs,
they would be forwarded "live". If anything else, the uploader would be a client
which reads the files in/var/log/journal/. The are advantages to both sol
Hi,
>> upload sounds a bit of a batch process, but thats just cosmetic wording.
>>
>> Having this in systems-journald and extend the forward to syslog config with
>> the
>> target
>> host was our expectation anyway.
> The difference is in how the logs are accessed: if journald itself does the
>
On Thu, Dec 11, 2014 at 02:54:18PM +, Holger Winkelmann [TP] wrote:
> HI,
>
> >> Are there any plans to follow? I.e, having all protocols in a generic
> >> gateway,
> >> or having one gateways per protocol? How the should we define which field
> >> form the journal should be forwarded to sysl
HI,
>> Are there any plans to follow? I.e, having all protocols in a generic
>> gateway,
>> or having one gateways per protocol? How the should we define which field
>> form the journal should be forwarded to syslog?
> IIUC, Lennart wanted to add this funcitonality to systemd-journal-upload or
>
On Thu, Dec 11, 2014 at 01:56:24PM +, Holger Winkelmann [TP] wrote:
> Hi,
>
> >> >However there is a need to forward log messages to remote syslog.
> >> >We try to avoid to introduce a full blown syslog solution
> >> >like i.e. rsyslog to just forward log messages to a remote syslog server.
>
Hi,
>> >However there is a need to forward log messages to remote syslog.
>> >We try to avoid to introduce a full blown syslog solution
>> >like i.e. rsyslog to just forward log messages to a remote syslog server.
> What Jóhann describes should work, even though it is a bit hacky.
> There is also
On Thu, Dec 11, 2014 at 10:55:27AM +, "Jóhann B. Guðmundsson" wrote:
>
> On 12/11/2014 10:28 AM, Holger Winkelmann [TP] wrote:
> >HI,
> >
> >Our embedded distribution relies on the systemd tooles including
> >journal based logging.
> >
> >However there is a need to forward log messages to remo
On 12/11/2014 10:28 AM, Holger Winkelmann [TP] wrote:
HI,
Our embedded distribution relies on the systemd tooles including
journal based logging.
However there is a need to forward log messages to remote syslog.
We try to avoid to introduce a full blown syslog solution
like i.e. rsyslog to jus
21 matches
Mail list logo
