On 02/28/2017 09:51 AM, bruce wrote:
> On Mon, Feb 27, 2017 at 11:44 PM, bruce wrote:
>> On Mon, Feb 27, 2017 at 2:56 PM, Rick Stevens wrote:
>>> On 02/27/2017 11:35 AM, Jon LaBadie wrote:
On Mon, Feb 27, 2017 at 09:41:11AM -0800, Rick Stevens wrote:
> On 02/26/2017 12:34 PM, bruce wrote
On Mon, Feb 27, 2017 at 11:44 PM, bruce wrote:
> On Mon, Feb 27, 2017 at 2:56 PM, Rick Stevens wrote:
>> On 02/27/2017 11:35 AM, Jon LaBadie wrote:
>>> On Mon, Feb 27, 2017 at 09:41:11AM -0800, Rick Stevens wrote:
On 02/26/2017 12:34 PM, bruce wrote:
> Hey Jon...
>
> You are abso
On Mon, Feb 27, 2017 at 2:56 PM, Rick Stevens wrote:
> On 02/27/2017 11:35 AM, Jon LaBadie wrote:
>> On Mon, Feb 27, 2017 at 09:41:11AM -0800, Rick Stevens wrote:
>>> On 02/26/2017 12:34 PM, bruce wrote:
Hey Jon...
You are absolutely correct.. if the parent ssh terminates.. the remo
On 02/27/2017 11:35 AM, Jon LaBadie wrote:
> On Mon, Feb 27, 2017 at 09:41:11AM -0800, Rick Stevens wrote:
>> On 02/26/2017 12:34 PM, bruce wrote:
>>> Hey Jon...
>>>
>>> You are absolutely correct.. if the parent ssh terminates.. the remote
> ...
>>
>> Jon, we try not to top-post here. Just a nudge
On Mon, Feb 27, 2017 at 09:41:11AM -0800, Rick Stevens wrote:
> On 02/26/2017 12:34 PM, bruce wrote:
> > Hey Jon...
> >
> > You are absolutely correct.. if the parent ssh terminates.. the remote
...
>
> Jon, we try not to top-post here. Just a nudge.
I didn't Rick, you attributed the above incor
On Mon, 27 Feb 2017 09:41:11 -0800
Rick Stevens wrote:
> If you are using ssh to spawn a remote screen session that runs a
> command in the background it should work just fine
Unless, of course, your ssh agent is being forwarded from way back
on the host system and you need the agent to be active
On 02/26/2017 12:34 PM, bruce wrote:
> Hey Jon...
>
> You are absolutely correct.. if the parent ssh terminates.. the remote
> process would "die".. In my use case, the remote process being fired
> off is actually being run under a remote "Screen" session, so it had
> better survive the ssh termin
Hey Jon...
You are absolutely correct.. if the parent ssh terminates.. the remote
process would "die".. In my use case, the remote process being fired
off is actually being run under a remote "Screen" session, so it had
better survive the ssh terminating!! (In testing, this has worked, so
I have n
On Sun, Feb 26, 2017 at 06:40:50PM +0100, Joachim Backes wrote:
> On 02/26/17 18:08, bruce wrote:
> > Morn guys...
> >
> > The following works as a test ssh to fire off a remote cmd. However it
> > waits for the cmd to complete befor returning. I'm looking to run th
> > cmd as a background on the
On 02/26/17 18:08, bruce wrote:
Morn guys...
The following works as a test ssh to fire off a remote cmd. However it
waits for the cmd to complete befor returning. I'm looking to run th
cmd as a background on the local/calling instance. Ultimaely, I'll be
testing this from py/php scripts.
ssh -t
Morn guys...
The following works as a test ssh to fire off a remote cmd. However it
waits for the cmd to complete befor returning. I'm looking to run th
cmd as a background on the local/calling instance. Ultimaely, I'll be
testing this from py/php scripts.
ssh -t user1@67.205.151.05 'cat /cloud/h
11 matches
Mail list logo