From: "Edwin Török" <edvin.torok@citrix.com> To: <xen-devel@lists.xenproject.org> Cc: "Edwin Török" <edwin.torok@cloud.com>, "Wei Liu" <wl@xen.org>, "Anthony PERARD" <anthony.perard@citrix.com> Subject: [PATCH] xenstored: do not redirect stderr to /dev/null Date: Wed, 25 Oct 2023 11:05:23 +0100 [thread overview] Message-ID: <87fbae122fd2d75852026d621358031c72c9a36d.1698227069.git.edwin.torok@cloud.com> (raw) From: Edwin Török <edwin.torok@cloud.com> By default stderr gets redirected to /dev/null because oxenstored daemonizes itself. This must be a left-over from pre-systemd days. In ee7815f49f ("tools/oxenstored: Set uncaught exception handler") a workaround was added to log exceptions directly to syslog to cope with standard error being lost. However it is better to not lose standard error (what if the connection to syslog itself fails, how'd we log that?), and use the '--no-fork' flag to do that. This flag is supported by both C and O versions of xenstored. Both versions also call sd_notify so there is no need for forking. Leave the default daemonize as is so that xenstored keeps working on non-Linux systems as before. Signed-off-by: Edwin Török <edwin.torok@cloud.com> --- tools/hotplug/Linux/init.d/sysconfig.xencommons.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/hotplug/Linux/init.d/sysconfig.xencommons.in b/tools/hotplug/Linux/init.d/sysconfig.xencommons.in index 433e4849af..09a1230cee 100644 --- a/tools/hotplug/Linux/init.d/sysconfig.xencommons.in +++ b/tools/hotplug/Linux/init.d/sysconfig.xencommons.in @@ -52,7 +52,7 @@ # like "--trace-file @XEN_LOG_DIR@/xenstored-trace.log" # See "@sbindir@/xenstored --help" for possible options. # Only evaluated if XENSTORETYPE is "daemon". -XENSTORED_ARGS= +XENSTORED_ARGS=--no-fork ## Type: string ## Default: Not defined, tracing off -- 2.41.0
WARNING: multiple messages have this Message-ID (diff)
From: "Edwin Török" <edvin.torok@citrix.com> To: <xen-devel@lists.xenproject.org> Cc: "Edwin Török" <edwin.torok@cloud.com>, "Wei Liu" <wl@xen.org>, "Anthony PERARD" <anthony.perard@citrix.com> Subject: [PATCH] xenstored: do not redirect stderr to /dev/null Date: Wed, 25 Oct 2023 14:50:54 +0100 [thread overview] Message-ID: <87fbae122fd2d75852026d621358031c72c9a36d.1698227069.git.edwin.torok@cloud.com> (raw) Message-ID: <20231025135054.jz5oWrByVytTrnWdOEMAxBsGpu5okRSoPzbMNB0Gdq4@z> (raw) From: Edwin Török <edwin.torok@cloud.com> By default stderr gets redirected to /dev/null because oxenstored daemonizes itself. This must be a left-over from pre-systemd days. In ee7815f49f ("tools/oxenstored: Set uncaught exception handler") a workaround was added to log exceptions directly to syslog to cope with standard error being lost. However it is better to not lose standard error (what if the connection to syslog itself fails, how'd we log that?), and use the '--no-fork' flag to do that. This flag is supported by both C and O versions of xenstored. Both versions also call sd_notify so there is no need for forking. Leave the default daemonize as is so that xenstored keeps working on non-Linux systems as before. Signed-off-by: Edwin Török <edwin.torok@cloud.com> --- tools/hotplug/Linux/init.d/sysconfig.xencommons.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/hotplug/Linux/init.d/sysconfig.xencommons.in b/tools/hotplug/Linux/init.d/sysconfig.xencommons.in index 433e4849af..09a1230cee 100644 --- a/tools/hotplug/Linux/init.d/sysconfig.xencommons.in +++ b/tools/hotplug/Linux/init.d/sysconfig.xencommons.in @@ -52,7 +52,7 @@ # like "--trace-file @XEN_LOG_DIR@/xenstored-trace.log" # See "@sbindir@/xenstored --help" for possible options. # Only evaluated if XENSTORETYPE is "daemon". -XENSTORED_ARGS= +XENSTORED_ARGS=--no-fork ## Type: string ## Default: Not defined, tracing off -- 2.41.0
next reply other threads:[~2023-10-25 10:06 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-25 10:05 Edwin Török [this message] 2023-10-25 13:50 ` [PATCH] xenstored: do not redirect stderr to /dev/null Edwin Török 2023-10-30 18:11 ` Edwin Torok
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=87fbae122fd2d75852026d621358031c72c9a36d.1698227069.git.edwin.torok@cloud.com \ --to=edvin.torok@citrix.com \ --cc=anthony.perard@citrix.com \ --cc=edwin.torok@cloud.com \ --cc=wl@xen.org \ --cc=xen-devel@lists.xenproject.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.