All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org
Subject: Re: regression in logger output to syslog
Date: Mon, 12 Oct 2015 15:34:51 +0200	[thread overview]
Message-ID: <20151012133451.GA6825@aepfle.de> (raw)
In-Reply-To: <20151012104414.GF2356@ws.net.home>

On Mon, Oct 12, Karel Zak wrote:

> On Fri, Oct 09, 2015 at 10:25:41AM +0200, Olaf Hering wrote:
> > I used a script with openSUSE 11.4 which called logger like this:
> > # logger -t "$l[$PPID] $i" "`sed -n ${c}p < $t`"
> > 
> > The tag was something like "me[123] foo: blah", and the number remained
> > stable for a single run.
> > 
> > Now with systemd and util-linux-2.26.2 the number does always change. 
> 
> Not sure if I understand the problem. How can logger update have any
> impact to the $PPID if this variable is generated by shell?

I'm sure the PPID variable itself is correct. But its value does not
appear anymore in journalctl -f.

>  $ logger --no-act --stderr --id=$PPID "this is message"
>  <13>Oct 12 12:40:07 kzak[1562]: this is message
>  $ logger --no-act --stderr --id=$PPID "this is message"
>  <13>Oct 12 12:40:07 kzak[1562]: this is message
> 
> .. still the same number. It seems that the problem is your script
> where is probably any fork/exec before logger call.

While having a 'journalctl -f &' running:

root@probook:~ # echo $PPID
2824
root@probook:~ # logger -t "me"  --id=$PPID "foo: blah"
root@probook:~ # Oct 12 15:29:55 probook.fritz.box me[6911]: foo: blah

root@probook:~ # logger -t "me"  --id=$PPID "foo: blah"
root@probook:~ # Oct 12 15:30:01 probook.fritz.box me[6912]: foo: blah
logger -t "me"  --id=$PPID "foo: blah"
root@probook:~ # Oct 12 15:30:05 probook.fritz.box me[6939]: foo: blah
root@probook:~ # logger -t "me" --no-act --stderr  --id=$PPID "foo: blah"
<13>Oct 12 15:32:26 me[2824]: foo: blah
root@probook:~ # logger -t "me" --no-act --stderr  --id=$PPID "foo: blah"
<13>Oct 12 15:32:28 me[2824]: foo: blah


So, its "systemd" who eats the required info.


Olaf

  reply	other threads:[~2015-10-12 13:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-09  8:25 regression in logger output to syslog Olaf Hering
2015-10-12 10:44 ` Karel Zak
2015-10-12 13:34   ` Olaf Hering [this message]
2015-10-21  9:37     ` Olaf Hering
2015-10-29 10:35       ` Karel Zak
2015-10-29 14:20         ` Olaf Hering
2015-10-29 14:36           ` Lennart Poettering
2015-10-29 15:32             ` Karel Zak

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20151012133451.GA6825@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=kzak@redhat.com \
    --cc=util-linux@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.