Timeline for How to automatically run commands on SSH login?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Jan 21, 2020 at 13:01 | history | suggested | NathanWindisch | CC BY-SA 4.0 |
Fixed a formatting error, and made the answer more clear.
|
| Jan 21, 2020 at 11:56 | review | Suggested edits | |||
| S Jan 21, 2020 at 13:01 | |||||
| Jul 26, 2019 at 12:29 | comment | added | clearlight | That could REALLY get someone into trouble if they didn't know what they are doing. It's potentially useful in corner cases, but that could REALLY mess someone up if they forgot they put commands there or the name and the path of that file. Gennerally it would be highly preferred to put the startup login commands in the expected place, .bashrc on the remote side and test for $SSH_CONNECTION, as other answers here have suggested. | |
| Jul 26, 2019 at 12:26 | comment | added | clearlight | docstore.mik.ua/orelly/networking_2ndEd/ssh/ch08_04.htm | |
| Nov 9, 2018 at 6:44 | comment | added | Daniel B | Not necessarily. It is a location where commands can be placed. | |
| Nov 9, 2018 at 6:41 | history | answered | brook hong | CC BY-SA 4.0 |