diff options
| author | Stefano Brivio <sbrivio@redhat.com> | 2022-01-26 16:39:33 +0100 |
|---|---|---|
| committer | Stefano Brivio <sbrivio@redhat.com> | 2022-01-28 18:51:50 +0100 |
| commit | 34e642923538a05ac21d7e7495da23fb0da56c5f (patch) | |
| tree | 7bf87c1259114dd95d05302d9fdc9aa985edbab7 /contrib/qemu/0001-net-Allow-also-UNIX-domain-sockets-to-be-used-as-net.patch | |
| parent | b1f5688495665269fb17732a3c7fb91c709e61b6 (diff) | |
| download | passt-34e642923538a05ac21d7e7495da23fb0da56c5f.tar passt-34e642923538a05ac21d7e7495da23fb0da56c5f.tar.gz passt-34e642923538a05ac21d7e7495da23fb0da56c5f.tar.bz2 passt-34e642923538a05ac21d7e7495da23fb0da56c5f.tar.lz passt-34e642923538a05ac21d7e7495da23fb0da56c5f.tar.xz passt-34e642923538a05ac21d7e7495da23fb0da56c5f.tar.zst passt-34e642923538a05ac21d7e7495da23fb0da56c5f.zip | |
passt, tap: Daemonise once socket is ready without waiting for connection
The existing behaviour is not really practical: an automated agent in
charge of starting both qemu and passt would need to fork itself to
start passt, because passt won't fork to background until qemu
connects, and the agent needs to unblock to start qemu.
Instead of waiting for a connection to daemonise, do it right away as
soon as a socket is available: that can be considered an initialised
state already.
Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
Diffstat (limited to 'contrib/qemu/0001-net-Allow-also-UNIX-domain-sockets-to-be-used-as-net.patch')
0 files changed, 0 insertions, 0 deletions