Timeline for RSH closing stderr socket with a delay?
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Sep 18, 2016 at 8:30 | history | bounty ended | nicoulaj | ||
| S Sep 18, 2016 at 8:30 | history | notice removed | nicoulaj | ||
| Sep 17, 2016 at 9:32 | vote | accept | nicoulaj | ||
| Sep 17, 2016 at 0:59 | answer | added | Gilbert | timeline score: 1 | |
| Sep 16, 2016 at 20:25 | comment | added | Chris Davies |
In that case, unless the question really is about the many sockets hitting TIME_WAIT and locking up the rsh daemon, please could you clarify what it is that you want to achieve with these many rsh invocations. It's difficult to suggest a work-around without knowing what you're trying to do.
|
|
| Sep 16, 2016 at 18:59 | comment | added | nicoulaj | I don't need to, I actually went with ssh. This is for data transfers within a safe, isolated cluster of machines, so security is not an issue. I could achieve better transfer speeds using rsh, because encryption cannot be disabled on ssh. rsh is the only "builtin" solution for transfering full speed from a remote machine AFAIK, otherwise you have to deploy your own daemon to serve the data. | |
| Sep 16, 2016 at 18:48 | comment | added | Chris Davies |
Do you really need to use rsh? Out of the box it's incredibly insecure and in almost all cases it can (and should) be replaced with ssh.
|
|
| S Sep 16, 2016 at 18:37 | history | bounty started | nicoulaj | ||
| S Sep 16, 2016 at 18:37 | history | notice added | nicoulaj | Draw attention | |
| Feb 24, 2016 at 11:45 | history | asked | nicoulaj | CC BY-SA 3.0 |