-
Notifications
You must be signed in to change notification settings - Fork 891
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
source ~/.cargo/env in .bashrc cause a machine failed as a rsync target #498
Comments
I don't quite understand what's going on here. What's causing rsync to fail? |
Non-interactive ssh sessions can pipe binary data through stdout (like rsync), so strings being printed out during session creation can break these protocols. We should just remove those strings. Besides, as one who opens a bunch of terminals, it gets a bit noisy to announce that rust is available. |
erickt
added a commit
to erickt/rustup.rs
that referenced
this issue
Jun 11, 2016
This printout can break non-interactive shells that use ssh to pipe binary data through stdout, like rsync. Plus it gets a bit noisy. Closes rust-lang#498
nodakai
pushed a commit
to nodakai/rustup.rs
that referenced
this issue
Apr 23, 2017
This printout can break non-interactive shells that use ssh to pipe binary data through stdout, like rsync. Plus it gets a bit noisy. Closes rust-lang#498
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
because of these output in ~/.cargo/env
It took me some time to find the problem.
maybe this not even an issue of rustup, but this really cause trouble to user.
The text was updated successfully, but these errors were encountered: