public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: Laine Stump <laine@redhat.com>
To: passt-dev@passt.top
Cc: Stefano Brivio <sbrivio@redhat.com>
Subject: Re: [PATCH v2 1/9] log to stderr until process is daemonized, even if a logfile is set
Date: Mon, 13 Feb 2023 22:41:56 -0500	[thread overview]
Message-ID: <daf029a9-ccd5-b247-358c-5a2727a0ec33@redhat.com> (raw)
In-Reply-To: <20230209184528.2473f854@elisabeth>

On 2/9/23 12:45 PM, Stefano Brivio wrote:
> On Wed,  8 Feb 2023 12:48:30 -0500
> Laine Stump <laine@redhat.com> wrote:
> 
>> Signed-off-by: Laine Stump <laine@redhat.com>
>> ---
>>   log.c   | 14 +++++++++++++-
>>   log.h   |  1 +
>>   passt.c |  6 ++++--
>>   3 files changed, 18 insertions(+), 3 deletions(-)
>>
>> diff --git a/log.c b/log.c
>> index 468c730..0ab0adf 100644
>> --- a/log.c
>> +++ b/log.c
>> @@ -34,6 +34,7 @@ static int	log_sock = -1;		/* Optional socket to system logger */
>>   static char	log_ident[BUFSIZ];	/* Identifier string for openlog() */
>>   static int	log_mask;		/* Current log priority mask */
>>   static int	log_opt;		/* Options for openlog() */
>> +static int	log_daemon_mode = false; /* true once process is daemonized */
>>   
>>   static int	log_file = -1;		/* Optional log file descriptor */
>>   static size_t	log_size;		/* Maximum log file size in bytes */
>> @@ -67,7 +68,8 @@ void name(const char *format, ...) {					\
>>   	}								\
>>   									\
>>   	if ((setlogmask(0) & LOG_MASK(LOG_DEBUG) ||			\
>> -	     setlogmask(0) == LOG_MASK(LOG_EMERG)) && log_file == -1) {	\
>> +	     setlogmask(0) == LOG_MASK(LOG_EMERG))			\
>> +	     && (log_file == -1 || !log_daemon_mode)) {			\
> 
> This is getting a bit complicated.
> 
> At the moment, LOG_EMERG is abused with the meaning "we don't know
> where/what to log yet", because we didn't process logging options yet.
> 
> Would it be an option to extend this abuse a bit further, and use
> LOG_EMERG to indicate that passt didn't daemonise yet, instead? You
> would just need to move the __setlogmask() calls in main(), and change
> the comment about the first one.

Well, the fact that I didn't understand this was what was being done 
with the log mask kind of indicates this abuse will be misunderstood in 
the long run :-P

But the abuse is already there, so it's not like I'm really making it 
any (much?) worse. It's just increasing the window when the logmask is 
set to LOG_EMERG, while modifying the log macro to not care if log_file 
is opened or not. I'll try that and see how it works out.

> 
> I haven't tested this, and we should be a bit careful with this (check
> what happens with and without running passt from an interactive
> terminal, with and without a log file, etc.).
> 
> A possibly cleaner approach could be to decouple this from the log
> mask, and have an enum instead, to represent logging "states" or
> "modes" -- but I'm not sure we're really going to save much complexity
> with it.

If I'm understanding you, that's kind of what I was doing, it's just 
that there are two modes - false == "logging before being daemonized" 
and true == "logging after being daemonized".

> 
> By the way, the man page should be updated as well.
> 

Good point.


  reply	other threads:[~2023-02-14  3:42 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-08 17:48 [PATCH v2 0/9] error logging fixes Laine Stump
2023-02-08 17:48 ` [PATCH v2 1/9] log to stderr until process is daemonized, even if a logfile is set Laine Stump
2023-02-09 17:45   ` Stefano Brivio
2023-02-14  3:41     ` Laine Stump [this message]
2023-02-08 17:48 ` [PATCH v2 2/9] add errexit() to log an error message and exit with a single call Laine Stump
2023-02-09 17:45   ` Stefano Brivio
2023-02-13  3:22     ` David Gibson
2023-02-13 10:46       ` Stefano Brivio
2023-02-08 17:48 ` [PATCH v2 3/9] eliminate most calls to usage() in conf() Laine Stump
2023-02-09 17:45   ` Stefano Brivio
2023-02-08 17:48 ` [PATCH v2 4/9] make conf_ports() exit immediately after logging error Laine Stump
2023-02-09 17:45   ` Stefano Brivio
2023-02-08 17:48 ` [PATCH v2 5/9] make conf_pasta_ns() " Laine Stump
2023-02-09 17:45   ` Stefano Brivio
2023-02-08 17:48 ` [PATCH v2 6/9] make conf_ugid() " Laine Stump
2023-02-13  4:23   ` Laine Stump
2023-02-08 17:48 ` [PATCH v2 7/9] make conf_netns_opt() " Laine Stump
2023-02-08 17:48 ` [PATCH v2 8/9] log a detailed error (not usage()) when there are extra non-option arguments Laine Stump
2023-02-09 17:45   ` Stefano Brivio
2023-02-08 17:48 ` [PATCH v2 9/9] convert all remaining err() followed by exit() to errexit() Laine Stump
2023-02-09 17:45   ` 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=daf029a9-ccd5-b247-358c-5a2727a0ec33@redhat.com \
    --to=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).