From: "Daniel P. Berrange" <berrange@redhat.com>
To: Sam <batmanustc@gmail.com>
Cc: qemu-devel@nongnu.org, qemu-discuss@nongnu.org
Subject: Re: [Qemu-devel] For unix domain socket, will only one client could connect to this socket?
Date: Thu, 27 Jul 2017 11:47:05 +0100 [thread overview]
Message-ID: <20170727104705.GJ2555@redhat.com> (raw)
In-Reply-To: <CAOE=1Z0VzZv5bstq+bZpnLMZx5sj-KUQMO3hQjM=R+17TiUOBA@mail.gmail.com>
On Thu, Jul 27, 2017 at 06:37:32PM +0800, Sam wrote:
> Hi all,
>
> I'm working on qemu-qga, and I want to send qmp command from this unix
> socket, but it hanged there(no response), I don't know if it's connect
> failed or something?
>
> [root@yf-mos-test-net09 ~]# socat
> > /opt/cloud/workspace/servers/f6fdd093-383b-444e-9bcf-dfa81794d465/qga.sock
> > readline
> > {"execute": "guest-execute", "session": "4768", "arguments": {"commands":
> > [{"command": "/bin/sh", "arguments": ["sh", "-c", "ping -c 1
> > 172.16.0.1"]}]}}
Pointless use of shell there. Just directly run ping
{"command": "/bin/ping", "arguments": ["-c", "1", "172.16.0.1"]}
>
>
> My question is, for tcp or udp socket, many client could connect to one
> server, is unix socket the same? Thank you~
You can only ever have a single client connected, even with tcp/unix
sockets backends.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2017-07-27 10:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-27 10:37 [Qemu-devel] For unix domain socket, will only one client could connect to this socket? Sam
2017-07-27 10:47 ` Daniel P. Berrange [this message]
2017-07-27 11:58 ` Sam
2017-07-27 13:52 ` Daniel P. Berrange
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=20170727104705.GJ2555@redhat.com \
--to=berrange@redhat.com \
--cc=batmanustc@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-discuss@nongnu.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.