Comments (7)
If you use the -i option ("inline"), both stdout and stderr are collected.
Also, the -e option can be used to write stderr to files. Since I don't
personally use the -P option, I don't have a strong opinion on whether it
should include stderr in addition to stdout. It would be nice to get feedback
from some more people that use -P. I'm just a bit nervous about breaking
things for other users.
Original comment by [email protected]
on 6 Mar 2011 at 8:06
- Added labels: Type-Enhancement
- Removed labels: Type-Defect
from parallel-ssh.
Thank you.
Original comment by [email protected]
on 6 Mar 2011 at 8:25
from parallel-ssh.
What do you think? Is the -i option enough, or would it be best if -P included
both stdout and stderr? Feel free to start a discussion on the mailing list if
you think this should be changed.
And thank you very much for your interest and participation with pssh.
Original comment by [email protected]
on 6 Mar 2011 at 10:43
from parallel-ssh.
Actually, I don't understand what --include flag does (explanation in --help or
in wiki could help). But flag works, and I just use it now.
I'm pretty sure that stdout and stderr should be either both shown or both
hidden. If you insist that -P behavior is correct, please at least replace
"output" with "stdout" word in --help output.
And I also think that that "Stderr: " prefix before stderr output is not
necessary. Bash or plain ssh do not output this prefix. If program running on
the server wants to tell something important, it just adds loud marker itself.
And again, thank you very much for pssh, it saved me a lot of time.
Original comment by [email protected]
on 6 Mar 2011 at 11:01
from parallel-ssh.
-i waits until command completes, I got it. Now I want -P to contain stderr
again :)
Original comment by [email protected]
on 6 Mar 2011 at 11:21
from parallel-ssh.
When you mentioned "--include", that was a typo for "--inline", right?
Anyway, I don't have strong feelings about whether -P does stderr as well as
stdout. I'd be inclined to agree that it would be reasonable for it to do
both, but as it's a change, I would want to be confident that it wouldn't
negatively affect other users of the option. I wouldn't be surprised if
everyone loves the idea, but I also wouldn't be surprised if someone came up
with a reason for the current behavior. Would you mind bringing this up on the
mailing list to see what everyone thinks?
Original comment by [email protected]
on 7 Mar 2011 at 4:59
from parallel-ssh.
So, I've never been too happy with the --print option because of the way that
it haphazardly interleaves output. I realized today that I think it can be
redeemed if each line of the output were preceded by the host name. This would
have to be a separate option. I think I would make two new options:
--print-stdout and --print-stderr. Here's an example:
$ pssh -H localhost --print-stderr ls /abc /root
stderr (localhost): ls: cannot access /abc: No such file or directory
stderr (localhost): ls: cannot open directory /root: Permission denied
[1] 12:41:29 [FAILURE] localhost Exited with error code 2
$
1) Would this do everything that you need?
2) Any thoughts on how the prefix should be formatted?
3) Any thoughts about how to deal with partial lines? A line of output might be
split into two pieces if it doesn't all arrive at the same time.
Original comment by [email protected]
on 23 Jan 2012 at 7:47
from parallel-ssh.
Related Issues (20)
- API module to enable easier use of PSSH as a library (patch included)
- TypeError when using Input script
- Erorr Code 255
- Not allowing relative paths makes no sense HOT 3
- pslurp can't use rsync HOT 2
- Patch: pass -o SendEnv in a way that is friendly on Mac OS HOT 1
- How to distribute different files to different hosts? HOT 1
- motd being printed only on debian squeeze boxes HOT 4
- SIGINFO handler gives task status HOT 1
- Manpage name problem HOT 1
- Sudo requires allocation of a real pseudoterminal HOT 6
- Installation errors: "setup.py install" HOT 1
- pslurp multiple files HOT 1
- Bandwith limit with pscp (parallel scp) HOT 4
- Summary of failed and successful execution HOT 2
- Teardown code in test classes is never called
- IPv6 host address processing broken
- Allow '-' as an alias for stdin
- cannot parse for more than one -O/-o options; cannot use -i option
- Crash on Archlinux/Python3.4 when asking for password (Includes one line fix) HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from parallel-ssh.