Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upqvm-run -p should redirect stdin and stdout separately #3074
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
marmarek
Sep 2, 2017
Member
If you don't want either stdin or stdout, use standard shell features: </dev/null or >/dev/null.
|
If you don't want either stdin or stdout, use standard shell features: |
marmarek
closed this
Sep 2, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
3hhh
Sep 7, 2017
True, but that makes e.g. bash aliases impossible.
In general I'd also recommend to opt-in to functionality rather than having to opt-out, but well...
3hhh
commented
Sep 7, 2017
|
True, but that makes e.g. bash aliases impossible. In general I'd also recommend to opt-in to functionality rather than having to opt-out, but well... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3hhh commentedSep 2, 2017
Every call to
qvm-run -predirects both stdin and stdout.Especially stdin is usually not necessary and may lead to unexpected behavior or even unexpected leaks from dom0 code.
Simple example:
This will break after the first run and make qvm-run read the entire list during the first iteration (I'm not sure whether it is actually passed to sys-usb?). It works without -p.
I'd recommend to introduce different flags for stdin and stdout or at least support a flag to disable the stdin redirect (ssh e.g. uses -n).
Similar issue with ssh: https://stackoverflow.com/questions/346445/bash-while-read-loop-breaking-early
Affects both 3.2 and 4.0rc1.