public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: passt-dev@passt.top, Laine Stump <laine@redhat.com>
Subject: Re: [PATCH] log: Don't duplicate messages on stderr before daemonising
Date: Thu, 16 Feb 2023 16:44:50 +1100	[thread overview]
Message-ID: <Y+3C0uSjTFpNYI4d@yekko> (raw)
In-Reply-To: <20230215115529.2157137-1-sbrivio@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 2542 bytes --]

On Wed, Feb 15, 2023 at 12:55:29PM +0100, Stefano Brivio wrote:
> Now that logging functions force printing messages to stderr before
> passt forks to background, we'll have duplicate messages when running
> from an interactive terminal, or if --stderr is passed, because at
> some point we set LOG_PERROR in our __openlog() wrapper.
> 
> We could defer setting LOG_PERROR, but that would change option
> semantics in other, unexpected ways. We could force calling
> passt_vsyslog() as long as the mask is set to LOG_EMERG, but that
> complicates the logic in logging functions even further.
> 
> Go the easy way for now: don't force printing to stderr with
> LOG_EMERG if LOG_PERROR is already set. We should seriously consider a
> rework of those logging functions at this point.
> 
> Signed-off-by: Stefano Brivio <sbrivio@redhat.com>

Reviewed-by: David Gibson <david@gibson.dropbear.id.au>

> ---
> This applies on top of Laine's series.
> 
>  log.c | 7 ++++---
>  1 file changed, 4 insertions(+), 3 deletions(-)
> 
> diff --git a/log.c b/log.c
> index 785bc36..f23e8ef 100644
> --- a/log.c
> +++ b/log.c
> @@ -44,6 +44,8 @@ static char	log_header[BUFSIZ];	/* File header, written back on cuts */
>  static time_t	log_start;		/* Start timestamp */
>  int		log_trace;		/* --trace mode enabled */
>  
> +#define BEFORE_DAEMON		(setlogmask(0) == LOG_MASK(LOG_EMERG))
> +
>  #define logfn(name, level, doexit)					\
>  void name(const char *format, ...) {					\
>  	struct timespec tp;						\
> @@ -56,8 +58,7 @@ void name(const char *format, ...) {					\
>  			tp.tv_nsec / (100L * 1000));			\
>  	}								\
>  									\
> -	if ((LOG_MASK(LOG_PRI(level)) & log_mask) ||			\
> -	    setlogmask(0) == LOG_MASK(LOG_EMERG)) {			\
> +	if ((LOG_MASK(LOG_PRI(level)) & log_mask) || BEFORE_DAEMON) {	\
>  		va_start(args, format);					\
>  		if (log_file != -1)					\
>  			logfile_write(level, format, args);		\
> @@ -67,7 +68,7 @@ void name(const char *format, ...) {					\
>  	}								\
>  									\
>  	if ((setlogmask(0) & LOG_MASK(LOG_DEBUG) && log_file == -1) ||	\
> -	     setlogmask(0) == LOG_MASK(LOG_EMERG)) {			\
> +	    (BEFORE_DAEMON && !(log_opt & LOG_PERROR))) {		\
>  		va_start(args, format);					\
>  		(void)vfprintf(stderr, format, args); 			\
>  		va_end(args);						\

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2023-02-16  5:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-15 11:55 [PATCH] log: Don't duplicate messages on stderr before daemonising Stefano Brivio
2023-02-16  5:44 ` David Gibson [this message]

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=Y+3C0uSjTFpNYI4d@yekko \
    --to=david@gibson.dropbear.id.au \
    --cc=laine@redhat.com \
    --cc=passt-dev@passt.top \
    --cc=sbrivio@redhat.com \
    /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).