On Sun, Oct 27, 2013 at 5:41 PM, Dimitris Zervas wrote:
> I have to say that I really hate journalctl.
> But apart from that, I need syslog.
> Journalctl requires too much resources (I have a 512MB KVM) and some times
> it kicks the server out of memory.
> Also, there is nearly no way to parse its
Op 27 okt. 2013 19:42 schreef "Dimitris Zervas" het
volgende:
>
> I have to say that I really hate journalctl.
> But apart from that, I need syslog.
[...]
According to [1] journald has an option sendtosyslog.
It might also be wise to keep a (small) journal available for those corner
cases that wi
On Sun, 27 Oct 2013 18:41:36 +0200
Dimitris Zervas wrote:
> I have to say that I really hate journalctl.
> But apart from that, I need syslog.
> Journalctl requires too much resources (I have a 512MB KVM) and some times
> it kicks the server out of memory.
I'm not sure what you mean. Does the sy
[2013-10-27 18:41:36 +0200] Dimitris Zervas:
> Journalctl requires too much resources (I have a 512MB KVM) and some times
> it kicks the server out of memory.
Unless you can refine your description of the problem, we can do nothing
to help than give suggestions blindly at random. Here's one: add t
I have to say that I really hate journalctl.
But apart from that, I need syslog.
Journalctl requires too much resources (I have a 512MB KVM) and some times
it kicks the server out of memory.
Also, there is nearly no way to parse its logs with any log analyzers, you
have to do it the hackish way wit
5 matches
Mail list logo