From: Wei Liu <wei.liu2@citrix.com>
To: Juergen Gross <jgross@suse.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
xen-devel@lists.xen.org, Wei Liu <wei.liu2@citrix.com>,
ian.jackson@eu.citrix.com, dave@recoil.org
Subject: Re: [PATCH 1/2] tools: remove systemd xenstore socket definitions
Date: Fri, 8 Jul 2016 14:02:28 +0100 [thread overview]
Message-ID: <20160708130228.GU416@citrix.com> (raw)
In-Reply-To: <577F9D5F.6030009@suse.com>
On Fri, Jul 08, 2016 at 02:32:31PM +0200, Juergen Gross wrote:
> On 08/07/16 14:15, Wei Liu wrote:
> > On Wed, Jun 29, 2016 at 03:00:41PM +0200, Juergen Gross wrote:
> >> On 29/06/16 14:52, Andrew Cooper wrote:
> >>> On 29/06/16 13:44, Juergen Gross wrote:
> >>>> @@ -2068,13 +1964,6 @@ int main(int argc, char *argv[])
> >>>> /* Tell the kernel we're up and running. */
> >>>> xenbus_notify_running();
> >>>>
> >>>> -#if defined(XEN_SYSTEMD_ENABLED)
> >>>> - if (systemd) {
> >>>> - sd_notify(1, "READY=1");
> >>>> - fprintf(stderr, SD_NOTICE "xenstored is ready\n");
> >>>> - }
> >>>> -#endif
> >>>
> >>> Getting rid of the socket configuration for systemd is ok, but we should
> >>> keep the sd_notify() calls for when the daemon is started by systemd.
> >>>
> >>> Socket activiation and sd_notify() are orthogonal, and sd_notify() is
> >>> still required if we don't want systemd to treat xenstored as a legacy
> >>> unix daemon.
> >>
> >> So what is the downside of xenstored being treated as a legacy daemon?
> >> This question is especially interesting for the case of patch 2 being
> >> considered: xenstored is no longer started by systemd, but by a wrapper
> >> script which might decide to start the xenstore domain instead.
> >>
> >> Another problem: today xenstored decides whether to call sd_notify()
> >> by testing the xenstore sockets being specified via systemd. This will
> >> no longer work. So how to do it now?
> >>
> >
> > Not sure I follow.
> >
> > See 81d758afca7c3c1e3ccbd78154b33d64fd7757fb. I expect systemd_checkin
> > to be able to tell if cxenstored is started by systemd or not.
> > sd_listen_fds doesn't seem to involve testing xenstore sockets. Do I
> > miss anything?
>
> Did you have a look at systemd_checkin()? It expects systemd does know
> exactly the number of sockets xenstored needs. Only if systemd knows
> about those sockets xenstored is regarded to have been started via
> systemd.
>
>
Ah, I see what you meant. I will let someone who is more familiar with
systemd to comment.
Wei.
> Juergen
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> https://lists.xen.org/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-07-08 13:02 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-29 12:44 [PATCH 0/2] tools: make xenstore domain/daemon configurable Juergen Gross
2016-06-29 12:44 ` [PATCH 1/2] tools: remove systemd xenstore socket definitions Juergen Gross
2016-06-29 12:52 ` Andrew Cooper
2016-06-29 13:00 ` Juergen Gross
2016-06-29 13:31 ` Ross Lagerwall
2016-06-29 13:44 ` Juergen Gross
2016-07-13 7:05 ` Juergen Gross
2016-07-20 9:02 ` Ross Lagerwall
2016-07-20 9:58 ` Juergen Gross
2016-07-20 10:52 ` George Dunlap
2016-07-20 11:12 ` Juergen Gross
2016-07-20 11:21 ` Andrew Cooper
2016-07-20 11:59 ` Juergen Gross
2016-07-20 12:08 ` Ian Jackson
2016-07-20 12:21 ` Juergen Gross
2016-07-20 12:32 ` Andrew Cooper
2016-07-20 13:02 ` Juergen Gross
2016-07-20 13:23 ` Ian Jackson
2016-07-20 13:29 ` George Dunlap
2016-07-20 14:09 ` Andrew Cooper
2016-07-20 12:11 ` Ian Jackson
2016-07-20 12:42 ` Juergen Gross
2016-07-08 12:15 ` Wei Liu
2016-07-08 12:32 ` Juergen Gross
2016-07-08 13:02 ` Wei Liu [this message]
2016-06-29 12:44 ` [PATCH 2/2] tools: make xenstore domain easy configurable Juergen Gross
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=20160708130228.GU416@citrix.com \
--to=wei.liu2@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=dave@recoil.org \
--cc=ian.jackson@eu.citrix.com \
--cc=jgross@suse.com \
--cc=xen-devel@lists.xen.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 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.