Util-Linux package development
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org, Lennart Poettering <lennart@poettering.net>
Subject: Re: regression in logger output to syslog
Date: Thu, 29 Oct 2015 15:20:21 +0100	[thread overview]
Message-ID: <20151029142021.GA9487@aepfle.de> (raw)
In-Reply-To: <20151029103532.GC19508@ws.net.home>

On Thu, Oct 29, Karel Zak wrote:

> On Wed, Oct 21, 2015 at 11:37:43AM +0200, Olaf Hering wrote:
> > On Mon, Oct 12, Olaf Hering wrote:
> > 
> > > So, its "systemd" who eats the required info.
> > 
> > In case you miss it:
> > 
> > ...
> > We do not allow faking syslog PID fields, for security reasons, it
> > will always be set to what the kernel passed to journald.
> > 
> > If this is something to support, then "logger" needs to to be patched so
> > that it can fake the SCM_CREDENTIALS metadata of the messages sent.
> > This requires privileges, but is not hard to do. Please file a bug
> > against util-linux and ask for for this to be added.
> 
>  Implemented, try logger(1) from util-linux git tree, please. 

Not sure what the "We" above refers to, but this change from 27a9eb5
may still not work for me:

+                   && geteuid() == 0 && kill(ctl->pid, 0) == 0) {

For me its required to run logger as non-root and still get the
specified number, like it used to do it years ago.

Olaf

  reply	other threads:[~2015-10-29 14:26 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
2015-10-21  9:37     ` Olaf Hering
2015-10-29 10:35       ` Karel Zak
2015-10-29 14:20         ` Olaf Hering [this message]
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=20151029142021.GA9487@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=kzak@redhat.com \
    --cc=lennart@poettering.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox