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

[Uoti Urpala]

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 people^maintainers
> with

I don't think "using it as a stick" is the right way to view it. My
view is just that you shouldn't consider it your problem if other pcre-
using packages haven't been updated. The functionality is useful enough
to enable on its own merits - it's not "using the package as a stick"
or anything like that.

If people want to make it a priority to only have one pcre lib, they
should work on updating the other packages. That doesn't mean you
should view depending on pcre2 to be "forcing" them to do that. Just
that if they don't, they'll have to live with 2 libs. And that's
perfectly reasonable, and preferable to the alternative of making it
your responsibility to update other packages or to hold back
dependencies on pcre2.


___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

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

[Michael Biebl]

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 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.
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890265
>
> OTOH the older libpcre is currently necessary due to dependencies such
> as grep, and the packages say people should migrate to libpcre2. So IMO
> it'd be reasonable to add a libpcre2 dependency, and respond to any
> complaints by saying that if people want to remove a pcre library, they
> should migrate the packages using the old version, so it could be
> removed instead.
>
> Keeping code using an up-to-date dependency disabled because other
> packages haven't been updated seems backwards...
>
>
> ___
> systemd-devel mailing list
> systemd-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/systemd-devel



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

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

[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 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. 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890265 

OTOH the older libpcre is currently necessary due to dependencies such
as grep, and the packages say people should migrate to libpcre2. So IMO
it'd be reasonable to add a libpcre2 dependency, and respond to any
complaints by saying that if people want to remove a pcre library, they
should migrate the packages using the old version, so it could be
removed instead.

Keeping code using an up-to-date dependency disabled because other
packages haven't been updated seems backwards...


___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

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

[Cecil Westerhof]

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...
>>
>
> Right, no need to file another bug report. https://bugs.debian.
> org/cgi-bin/bugreport.cgi?bug=890265
>

Indeed not. Seeing that the last message is from three months ago, I am
afraid it will not be solved in the near future.

-- 
Cecil Westerhof
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

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

[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...
>

Right, no need to file another bug report.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890265
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

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

[Jérémy Rosen]

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 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 feature. It's a big project, and posts
in other venues (newsgroups, mailing lists, IRC channels, forums, bathroom
walls, etc.) are likely to get lost, or not be read by the right people who
would do the work.

Thanks,
 smcv
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel


--
SMILE 

20 rue des Jardins
92600 Asnières-sur-Seine


*Jérémy ROSEN*
Architecte technique
Responsable de l'expertise Smile-ECS

email jeremy.ro...@smile.fr 
phone +33141402967
url http://www.smile.eu

Twitter  Facebook 
 LinkedIn 
 Github 




Découvrez l’univers Smile, rendez-vous sur smile.eu 



eco Pour la planète, n'imprimez ce mail que si c'est nécessaire
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

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

[Simon McVittie]

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 feature. It's a big project, and posts
in other venues (newsgroups, mailing lists, IRC channels, forums, bathroom
walls, etc.) are likely to get lost, or not be read by the right people who
would do the work.

Thanks,
smcv
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

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

[Cecil Westerhof]

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 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?
>
> Since version 237, journalctl has had a --grep option.
>
> Message text is not indexed, so performance-wise this still requires
> going through all messages (as limited by other options).
>

On Debian the version is 232, but backports has 237. Sadly this gives:
Compiled without pattern matching support

That is because:
regex in journalctl is an optional feature that is decided at compile
time

Posted the problem in a Debian newsgroup. Fingers crossed that they are
going to enable it.

-- 
Cecil Westerhof
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

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

[Jérémy Rosen]

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 support, 
but that's a bit more complicated


(btw, you only replied to me, not the mailing list. Not a big deal, just 
pointing it out so you don't forward further questions just to me)


On 30/08/2018 12:02, Cecil Westerhof wrote:

2018-08-30 9:57 GMT+02:00 Jérémy Rosen :


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


That makes it even more interesting.

I need to know why I get:
 Compiled without pattern matching support

and what to do about it.



--
SMILE 

20 rue des Jardins
92600 Asnières-sur-Seine


*Jérémy ROSEN*
Architecte technique
Responsable de l'expertise Smile-ECS

email jeremy.ro...@smile.fr 
phone +33141402967
url http://www.smile.eu

Twitter  Facebook 
 LinkedIn 
 Github 




Découvrez l’univers Smile, rendez-vous sur smile.eu 



eco Pour la planète, n'imprimez ce mail que si c'est nécessaire
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

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

[Jérémy Rosen]

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, 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, or am I overlooking something?

Since version 237, journalctl has had a --grep option.

Message text is not indexed, so performance-wise this still requires
going through all messages (as limited by other options).


___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel


--
SMILE 

20 rue des Jardins
92600 Asnières-sur-Seine


*Jérémy ROSEN*
Architecte technique
Responsable de l'expertise Smile-ECS

email jeremy.ro...@smile.fr 
phone +33141402967
url http://www.smile.eu

Twitter  Facebook 
 LinkedIn 
 Github 




Découvrez l’univers Smile, rendez-vous sur smile.eu 



eco Pour la planète, n'imprimez ce mail que si c'est nécessaire
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

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

[Uoti Urpala]

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, or am I overlooking something?

Since version 237, journalctl has had a --grep option.

Message text is not indexed, so performance-wise this still requires
going through all messages (as limited by other options).


___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] Select on value of log message

[Cecil Westerhof]

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
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel