diff options
| author | Alyssa Ross <hi@alyssa.is> | 2021-03-24 18:21:34 +0000 |
|---|---|---|
| committer | Alyssa Ross <hi@alyssa.is> | 2021-03-24 19:50:12 +0000 |
| commit | 8d75b0f46a367318c634f71a5a964cdbb9578977 (patch) | |
| tree | 945af01ee23fa148d166bbdfe656392163b1575e /vsock.h | |
| parent | d24ff2d26aa45cb53f492a3f18ba6ce8a76f9d7d (diff) | |
| download | ucspi-vsock-master.tar ucspi-vsock-master.tar.gz ucspi-vsock-master.tar.bz2 ucspi-vsock-master.tar.lz ucspi-vsock-master.tar.xz ucspi-vsock-master.tar.zst ucspi-vsock-master.zip | |
I found myself running
vsockclient 2 1024 true
in a situation where it just mattered that a connection was made, and
no data needed to be exchanged of it. That I found myself doing this
is quite a strong indicator that the program to exec into should be
optional.
UCSPI-1996[1] doesn't specify what should happen if no application is
provided, so I think this is a reasonable interpretation. I'm not
sure if I feel the same for vsockserver(d), so I haven't made the
corresponding change there. I'll wait to see if there's ever a need
for it.
[1]: https://cr.yp.to/proto/ucspi.txt
Message-Id: <20210324182433.19110-1-hi@alyssa.is>
Reviewed-by: Cole Helbling <cole.e.helbling@outlook.com>
Diffstat (limited to 'vsock.h')
0 files changed, 0 insertions, 0 deletions