Your message dated Thu, 15 Mar 2018 18:09:25 +0100 with message-id <630c41a4-828b-4796-a8c5-c3a5d4813...@debian.org> and subject line Re: Bug#893014: systemd: journalctl -g and --grep fail (in different ways) has caused the Debian Bug report #893014, regarding systemd: journalctl -g and --grep fail (in different ways) to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 893014: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893014 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: systemd Version: 237-4 Severity: normal journalctl(1) says: -g, --grep= Filter output to entries where the MESSAGE= field matches the specified regular expression. PERL-compatible regular expressions are used, see pcre2pattern(3) for a detailed description of the syntax. If the pattern is all lowercase, matching is case insensitive. Otherwise, matching is case sensitive. This can be overridden with the --case-sensitive option, see below. however: 0 dkg@alice:~$ journalctl --grep=hello Compiled without pattern matching support 0 dkg@alice:~$ journalctl -g hello journalctl: invalid option -- 'g' 1 dkg@alice:~$ note that --grep=hello returns 0 and provides a user-comprehensible warning about why it didn't work. but -g hello returns 1 and just gives an incomprehensible error message that doesn't indicate why it's failing. I think the right approach would be to return a non-zero error code in both cases, and to print the same reasonable explanation in both cases. --dkg -- Package-specific info: -- System Information: Debian Release: buster/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing'), (500, 'oldstable'), (200, 'unstable-debug'), (200, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages systemd depends on: ii adduser 3.117 ii libacl1 2.2.52-3+b1 ii libapparmor1 2.12-3 ii libaudit1 1:2.8.2-1 ii libblkid1 2.31.1-0.4 ii libc6 2.27-1 ii libcap2 1:2.25-1.2 ii libcryptsetup12 2:2.0.1-1 ii libgcrypt20 1.8.1-4 ii libgpg-error0 1.27-6 ii libidn11 1.33-2.1 ii libip4tc0 1.6.2-1 ii libkmod2 25-1 ii liblz4-1 0.0~r131-2+b1 ii liblzma5 5.2.2-1.3 ii libmount1 2.31.1-0.4 ii libpam0g 1.1.8-3.7 ii libseccomp2 2.3.1-2.1 ii libselinux1 2.7-2+b1 ii libsystemd0 237-4 ii mount 2.31.1-0.4 ii procps 2:3.3.12-4 ii util-linux 2.31.1-0.4 Versions of packages systemd recommends: ii dbus 1.12.6-2 ii libpam-systemd 237-4 Versions of packages systemd suggests: ii policykit-1 0.105-18 ii systemd-container 237-4 Versions of packages systemd is related to: ii dracut 047-2 pn initramfs-tools <none> ii udev 237-4 -- Configuration Files: /etc/systemd/resolved.conf changed [not included] -- no debconf information
--- End Message ---
--- Begin Message ---Version: 238-1 Am 15.03.2018 um 15:39 schrieb Daniel Kahn Gillmor: > Package: systemd > Version: 237-4 > Severity: normal > > journalctl(1) says: > > -g, --grep= > Filter output to entries where the MESSAGE= field matches the > specified regular expression. PERL-compatible regular expressions > are used, see pcre2pattern(3) for a detailed description of the > syntax. > > If the pattern is all lowercase, matching is case insensitive. > Otherwise, matching is case sensitive. This can be overridden with > the --case-sensitive option, see below. > > > however: > > 0 dkg@alice:~$ journalctl --grep=hello > Compiled without pattern matching support > 0 dkg@alice:~$ journalctl -g hello > journalctl: invalid option -- 'g' > 1 dkg@alice:~$ > > > note that --grep=hello returns 0 and provides a user-comprehensible > warning about why it didn't work. > > but -g hello returns 1 and just gives an incomprehensible error > message that doesn't indicate why it's failing. > > I think the right approach would be to return a non-zero error code in > both cases, and to print the same reasonable explanation in both > cases. > -g was not supported in v237, that's why you get a different error message. This is fixed in v238 though by commit 2de6b06b272b2b89035c67d879f330e3c70ba6b3 Author: Douglas Christman <douglaschrist...@gmail.com> Date: Tue Feb 27 20:16:26 2018 -0500 journalctl: make journalctl -g work as documented Add "g" to optstring so both "--grep" and "-g" work with journalctl -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
_______________________________________________ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
