Re: [systemd-devel] Select on value of log message

On Thu, 2018-08-30 at 19:32 +0200, Michael Biebl wrote: > Am Do., 30. Aug. 2018 um 18:56 Uhr schrieb Uoti Urpala > : > > Keeping code using an up-to-date dependency disabled because other > > packages haven't been updated seems backwards... > I don't want to use systemd as a stick to beat

Re: [systemd-devel] Select on value of log message

I don't want to use systemd as a stick to beat people^maintainers with Am Do., 30. Aug. 2018 um 18:56 Uhr schrieb Uoti Urpala : > > On Thu, 2018-08-30 at 16:39 +0200, Michael Biebl wrote: > > Am Do., 30. Aug. 2018 um 15:50 Uhr schrieb Jérémy Rosen < > > jeremy.ro...@smile.fr>: > > > I *think* that

Re: [systemd-devel] Select on value of log message

On Thu, 2018-08-30 at 16:39 +0200, Michael Biebl wrote: > Am Do., 30. Aug. 2018 um 15:50 Uhr schrieb Jérémy Rosen < > jeremy.ro...@smile.fr>: > > I *think* that it's deactivated in debian because journalctl is a > > core package and debian doesn't want to pull the regex library into > > it's

Re: [systemd-devel] Select on value of log message

2018-08-30 16:39 GMT+02:00 Michael Biebl : > > > Am Do., 30. Aug. 2018 um 15:50 Uhr schrieb Jérémy Rosen < > jeremy.ro...@smile.fr>: > >> I *think* that it's deactivated in debian because journalctl is a core >> package and debian doesn't want to pull the regex library into it's core... >> > >

Re: [systemd-devel] Select on value of log message

Am Do., 30. Aug. 2018 um 15:50 Uhr schrieb Jérémy Rosen < jeremy.ro...@smile.fr>: > I *think* that it's deactivated in debian because journalctl is a core > package and debian doesn't want to pull the regex library into it's core... > Right, no need to file another bug report.

Re: [systemd-devel] Select on value of log message

I *think* that it's deactivated in debian because journalctl is a core package and debian doesn't want to pull the regex library into it's core... not sure, though. They'll probably tell you in the bug report you opened. On 30/08/2018 15:41, Simon McVittie wrote: On Thu, 30 Aug 2018 at

Re: [systemd-devel] Select on value of log message

On Thu, 30 Aug 2018 at 12:48:02 +0200, Cecil Westerhof wrote: > Posted the problem in a Debian newsgroup. Please send all Debian-specific bug reports and feature requests to its bug tracking system , filed against the package that has the bug or is missing the

Re: [systemd-devel] Select on value of log message

Sadly sometimes GMail messes up reply. All my replies went to individuals instead of the mailing list. %<{ I give the most important things I wrote. 2018-08-29 20:09 GMT+02:00 Uoti Urpala : > On Wed, 2018-08-29 at 19:49 +0200, Cecil Westerhof wrote: > > There are a lot of ways you can select

Re: [systemd-devel] Select on value of log message

unfortunately, regex in journalctl is an optional feature that is decided at compile time. Your distro probably did not compile that support. The best approch would be to open a feature request on your distro's bugtracker. Alternatively you can recompile systemd yourself and add that

Re: [systemd-devel] Select on value of log message

One of the big advantage of --grep compared to |grep is that it returns the whole message, not just the line containig your regex so you can combine it with "-o verbose" and get all the info on the message easily On 29/08/2018 20:09, Uoti Urpala wrote: On Wed, 2018-08-29 at 19:49 +0200,

Re: [systemd-devel] Select on value of log message

On Wed, 2018-08-29 at 19:49 +0200, Cecil Westerhof wrote: > There are a lot of ways you can select the output you get from > journalctl, but it seems you cannot select on the message itself. > That is why I need to do something like: > journalctl | grep 'Database is locked' > > Is this true,

[systemd-devel] Select on value of log message

There are a lot of ways you can select the output you get from journalctl, but it seems you cannot select on the message itself. That is why I need to do something like: journalctl | grep 'Database is locked' Is this true, or am I overlooking something? -- Cecil Westerhof