qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Richard W.M. Jones" <rjones@redhat.com>
Cc: qemu-devel@nongnu.org, den@openvz.org, rkagan@virtuozzo.com,
	dplotnikov@virtuozzo.com, berrange@redhat.com,
	stefanha@gmail.com
Subject: Re: [Qemu-devel] [PATCH v3] qemu-nbd: Implement socket activation.
Date: Fri, 3 Feb 2017 09:31:43 -0800	[thread overview]
Message-ID: <2f5ef524-02d7-e0e8-c693-db932f8270b9@redhat.com> (raw)
In-Reply-To: <20170203170925.12554-2-rjones@redhat.com>



On 03/02/2017 09:09, Richard W.M. Jones wrote:
> +                                                   const char *port,
> +                                                   bool fork_process)
> +{
> +    if (device != NULL) {
> +        return "NBD device can't be set when using socket activation";
> +    }
> +
> +    if (sockpath != NULL) {
> +        return "Unix socket can't be set when using socket activation";
> +    }
> +
> +    if (address != NULL) {
> +        return "The interface can't be set when using socket activation";
> +    }
> +
> +    if (port != NULL) {
> +        return "TCP port number can't be set when using socket activation";
> +    }
> +
> +    if (fork_process) {
> +        return "Fork (--fork) can't be used with socket activation";
> +    }

Why not?  You could have a Type=forking foo.service, which makes little
sense but would work.

Apart from this, the patch seems fine.

> +    return NULL;
> +}

  reply	other threads:[~2017-02-03 17:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-03 17:09 [Qemu-devel] [PATCH v3] qemu-nbd: Implement socket activation Richard W.M. Jones
2017-02-03 17:09 ` Richard W.M. Jones
2017-02-03 17:31   ` Paolo Bonzini [this message]
2017-02-03 18:56     ` Richard W.M. Jones
2017-02-03 18:58       ` Paolo Bonzini
2017-02-03 19:22         ` Richard W.M. Jones
2017-02-04  7:44           ` Paolo Bonzini

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=2f5ef524-02d7-e0e8-c693-db932f8270b9@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=berrange@redhat.com \
    --cc=den@openvz.org \
    --cc=dplotnikov@virtuozzo.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rjones@redhat.com \
    --cc=rkagan@virtuozzo.com \
    --cc=stefanha@gmail.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.
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 NNTP newsgroup(s).