Timeline for Detecting that a script is run within ARD
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 21, 2012 at 8:11 | comment | added | Scot | Thanks again. For the purposes of this script, I wanted to have the logic built-in to the script itself, so I ended up using the environment variable TERM (it is dumb when running a script within ARD, and xterm-256color when running locally. So far this has been a good enough hook... | |
| Dec 19, 2012 at 23:25 | comment | added | bmike♦ | @Scot Here's an example of parsing arguments from a shell script if you're not familiar with that side of scripting. | |
| Dec 19, 2012 at 23:24 | history | edited | bmike♦ | CC BY-SA 3.0 |
include a sample script to assist in logging of remote commands
|
| Dec 19, 2012 at 5:37 | comment | added | Scot | Thanks, I may resort to that - though I had been hoping that I could seamlessly use the same script in both places - it needs to act differently in each place. I'm looking through the environment variables, and may have found a couple options that may be sufficient for my needs (COLUMNS or TERM) - though I'm still interested in a proper method, if it exists... | |
| Dec 19, 2012 at 1:54 | history | answered | bmike♦ | CC BY-SA 3.0 |