public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: Stefano Brivio <sbrivio@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: Laine Stump <laine@redhat.com>, passt-dev@passt.top
Subject: Re: [PATCH v4 1/9] log to stderr until process is daemonized, even if a log file is set
Date: Thu, 16 Feb 2023 18:50:31 +0100	[thread overview]
Message-ID: <20230216185031.7d71029d@elisabeth> (raw)
In-Reply-To: <Y+2/jcuQnylAISB5@yekko>

On Thu, 16 Feb 2023 16:30:53 +1100
David Gibson <david@gibson.dropbear.id.au> wrote:

> On Wed, Feb 15, 2023 at 03:24:29AM -0500, Laine Stump wrote:
> > Once a log file (specified on the commandline) is opened, the logging
> > functions will stop sending error logs to stderr, which is annoying if
> > passt has been started by another process that wants to collect error
> > messages from stderr so it can report why passt failed to start. It
> > would be much nicer if passt continued sending all log messages to
> > stderr until it daemonizes itself (at which point the process that
> > started passt can assume that it was started successfully).
> > 
> > The system log mask is set to LOG_EMERG when the process starts, and
> > we're already using that to do "special" logging during the period
> > from process start until the log level requested on the commandline is
> > processed (setting the log mask to something else). This period
> > *almost* matches with "the time before the process is daemonized"; if
> > we just delay setting the log mask a tiny bit, then it will match
> > exactly, and we can use it to determine if we need to send log
> > messages to stderr even when a log file has been specified and opened.
> > 
> > This patch delays the setting of the log mask until immediately before
> > the call to __daemon(). It also modifies logfn() slightly, so that it
> > will log to stderr any time log mask is LOG_EMERG, even if a log file
> > has been opened.
> > 
> > Signed-off-by: Laine Stump <laine@redhat.com>  
> 
> Reviewed-by: David Gibson <david@gibson.dropbear.id.au>

Sorry David, I missed to add *all* your Reviewed-by tags on this
series. :/ Thanks a lot for reviewing all this.

-- 
Stefano


  reply	other threads:[~2023-02-16 17:50 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-15  8:24 [PATCH v4 0/9] error logging fixes Laine Stump
2023-02-15  8:24 ` [PATCH v4 1/9] log to stderr until process is daemonized, even if a log file is set Laine Stump
2023-02-15 11:54   ` Stefano Brivio
2023-02-16  5:30   ` David Gibson
2023-02-16 17:50     ` Stefano Brivio [this message]
2023-02-15  8:24 ` [PATCH v4 2/9] add die() to log an error message and exit with a single call Laine Stump
2023-02-16  5:31   ` David Gibson
2023-02-15  8:24 ` [PATCH v4 3/9] eliminate most calls to usage() in conf() Laine Stump
2023-02-16  5:34   ` David Gibson
2023-02-15  8:24 ` [PATCH v4 4/9] make conf_ports() exit immediately after logging error Laine Stump
2023-02-16  5:36   ` David Gibson
2023-02-15  8:24 ` [PATCH v4 5/9] make conf_pasta_ns() " Laine Stump
2023-02-16  5:37   ` David Gibson
2023-02-15  8:24 ` [PATCH v4 6/9] make conf_ugid() " Laine Stump
2023-02-16  5:38   ` David Gibson
2023-02-15  8:24 ` [PATCH v4 7/9] make conf_netns_opt() " Laine Stump
2023-02-16  5:38   ` David Gibson
2023-02-15  8:24 ` [PATCH v4 8/9] log a detailed error (not usage()) when there are extra non-option arguments Laine Stump
2023-02-16  5:39   ` David Gibson
2023-02-15  8:24 ` [PATCH v4 9/9] convert all remaining err() followed by exit() to die() Laine Stump
2023-02-16  5:40   ` David Gibson
2023-02-15 11:56 ` [PATCH v4 0/9] error logging fixes Stefano Brivio
2023-02-16 22:21 ` Stefano Brivio

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=20230216185031.7d71029d@elisabeth \
    --to=sbrivio@redhat.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=laine@redhat.com \
    --cc=passt-dev@passt.top \
    /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.
Code repositories for project(s) associated with this public inbox

	https://passt.top/passt

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for IMAP folder(s).