From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: util-linux-owner@vger.kernel.org Received: from mx1.redhat.com ([209.132.183.28]:38275 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751178AbbJLKoR (ORCPT ); Mon, 12 Oct 2015 06:44:17 -0400 Date: Mon, 12 Oct 2015 12:44:14 +0200 From: Karel Zak To: Olaf Hering Cc: util-linux@vger.kernel.org Subject: Re: regression in logger output to syslog Message-ID: <20151012104414.GF2356@ws.net.home> References: <20151009082541.GA9068@aepfle.de> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 In-Reply-To: <20151009082541.GA9068@aepfle.de> Sender: util-linux-owner@vger.kernel.org List-ID: 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? > IfI understand the man page correctly this is supposed to achieve the > same, but the $PPID never made it into journalctl -f outout: > > logger -t "me" --id=$PPID "foo: blah" $ 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. Maybe you need to save the PID at the begin of the script: #!/bin/bash REPORTED_PID=$$ ... your script ... logger --id=$REPORTED_PID "foo: blah" Karel -- Karel Zak http://karelzak.blogspot.com