| 1 |
On Wed, Sep 09, 2009 at 06:11:20PM +0530, Penguin Lover Kaushal Shriyan squawked: |
| 2 |
> > file `which autossh` |
| 3 |
|
| 4 |
What about this command? I want to see if autossh is a wrapper script |
| 5 |
so that it has its own environment. |
| 6 |
|
| 7 |
> $ AUTOSSH_POLL=100 autossh hostxxx |
| 8 |
> autossh[16050]: checking for grace period, tries = 0 |
| 9 |
> autossh[16050]: starting ssh (count 1) |
| 10 |
> autossh[16053]: execing /usr/bin/ssh |
| 11 |
> autossh[16050]: ssh child pid is 16053 |
| 12 |
> autossh[16050]: check on child 16053 |
| 13 |
> autossh[16050]: set alarm for 600 secs |
| 14 |
> ^Cautossh[16050]: received signal to exit (2) |
| 15 |
|
| 16 |
Regardless, you should file a bug. The way it is ignoring the |
| 17 |
environmental variable is definitely different from what the man page |
| 18 |
says it should do. |
| 19 |
|
| 20 |
The only things I can think of that gives it such behaviour is either |
| 21 |
|
| 22 |
(i) The software itself is broken and doesn't respect the variable. |
| 23 |
(ii) /usr/bin/autossh is actually a wrapper script so you need to set |
| 24 |
the variables in there, instead of in your .bashrc. |
| 25 |
|
| 26 |
For either case, the behaviour is not consistent with the man page. |
| 27 |
|
| 28 |
W |
| 29 |
-- |
| 30 |
M: Hey, do that again! Make the computer beep... |
| 31 |
W: As you wish! |
| 32 |
M: ah~~ ah~~... hum, that beep was a G. |
| 33 |
W: how can you tell? |
| 34 |
(turn around) |
| 35 |
oh... no fair... a tuner |
| 36 |
Sortir en Pantoufles: up 1006 days, 16:16 |
Archives