Hi.
On Thu, 20 Dec 2018 23:36:08 +0100 "Patrick Dupre" wrote:
> I would like to run a process on a remote machine (login through ssh
> and then su) which will remian running even when I close the connection.
You can use systemd-run: your process will be run as a systemd
service.
In addition to
Patrick Dupre wrote:
> Hello,
>
> I would like to run a process on a remote machine (login through ssh
> and then su) which will remian running even when I close the connection.
>
> I am not sure that a standard background process (using &) is not going to
> kill
On 20Dec2018 15:16, Dave Stevens wrote:
On Thu, 20 Dec 2018 23:10:47 +
Rick Stevens wrote:
I am not sure that a standard background process (using &) is not
going to
> kill the process when I logout.
Make sure you have the screen RPM installed on the remote machine,
then you can
Or if you want something lighter weight, you could use
the bg-dammit program from my web page:
https://tomhorsley.com/game/Mjolnir.html
It is similar to nohup, but it really really backgrounds things.
___
users mailing list -- users@lists.fedoraproject.
On Thu, 20 Dec 2018 23:10:47 +
Rick Stevens wrote:
> I am not sure that a standard background process (using &) is not
> going to
> > kill the process when I logout.
>
> Make sure you have the screen RPM installed on the remote machine,
> then you can run the co
On 12/20/18 2:36 PM, Patrick Dupre wrote:
> Hello,
>
> I would like to run a process on a remote machine (login through ssh
> and then su) which will remian running even when I close the connection.
>
> I am not sure that a standard background process (using &) is not going
On 20.12.18 23:36, Patrick Dupre wrote:
> I would like to run a process on a remote machine (login through ssh
> and then su) which will remian running even when I close the connection.
run you command using nohup.
best regards
Ulf
___
users mailing li
On 12/21/18 6:36 AM, Patrick Dupre wrote:
> I would like to run a process on a remote machine (login through ssh
> and then su) which will remian running even when I close the connection.
>
> I am not sure that a standard background process (using &) is not going to
> kill
Hello,
I would like to run a process on a remote machine (login through ssh
and then su) which will remian running even when I close the connection.
I am not sure that a standard background process (using &) is not going to
kill the process when I logout.
T
Can't Ansible be used to achieve your objective?
Br,
-vu
On Sat, Mar 4, 2017 at 6:28 PM, Cameron Simpson wrote:
> On 04Mar2017 13:34, bruce wrote:
>
>> tried the SSH without the "-t"...
>>
>> ssh -vvv crawl_user@67.205.151.11 "ls /crawl_tmp;" &
>>
>> this works -- no prob... returns as expect
On 04Mar2017 13:34, bruce wrote:
tried the SSH without the "-t"...
ssh -vvv crawl_user@67.205.151.11 "ls /crawl_tmp;" &
this works -- no prob... returns as expected...
this doesn't..
ssh -vvv -t crawl_user@67.205.151.11 "ls /crawl_tmp;"
Well, it has no trailing "&"...
-t causes the _rem
gt;
> foreach iplist as ipaddress
>
> ssh user1@ipaddress command & (assuming that the '&' runs the local
> ssh in the background -- it doesn't!)
>
>
> Running "stuff" on the remote can occur in a "Screen" session, which
> w
On Sat, Mar 4, 2017 at 1:28 PM, bruce wrote:
> On Sat, Mar 4, 2017 at 11:09 AM, Tom Horsley wrote:
>> On Sat, 4 Mar 2017 09:41:31 -0500
>> bruce wrote:
>>
>>> ssh user1@ipaddress command & (assuming that the '&' runs the local
>>> ssh in the background -- it doesn't!)
>>
>> I have no idea how i
On Sat, Mar 4, 2017 at 11:09 AM, Tom Horsley wrote:
> On Sat, 4 Mar 2017 09:41:31 -0500
> bruce wrote:
>
>> ssh user1@ipaddress command & (assuming that the '&' runs the local
>> ssh in the background -- it doesn't!)
>
> I have no idea how it could fail to run it in the background,
> unless perh
On Sat, 4 Mar 2017 09:41:31 -0500
bruce wrote:
> ssh user1@ipaddress command & (assuming that the '&' runs the local
> ssh in the background -- it doesn't!)
I have no idea how it could fail to run it in the background,
unless perhaps it is stopping because it is asking for tty input.
You can fi
he status and number, and then reports the total time it took to
complete.
Again, plink is part of putty, so need to install putty if it isn't already.
On 4 Mar 2017 at 9:41, bruce wrote:
From: bruce
Date sent: Sat, 4 Mar 2017 09:41:31 -0500
Subject:
kground -- it doesn't!)
Running "stuff" on the remote can occur in a "Screen" session, which
would allow the ssh process to fire off the remote cmd, but it still
doesn't run the local ssh as a "background" process..
17 matches
Mail list logo