Difference between revisions of "Talk:Allow a program to continue after logoff"

From ArchWiki
Jump to: navigation, search
 
(4 intermediate revisions by 3 users not shown)
Line 1: Line 1:
==xpra==
+
Cannot use this feature:
xpra is available in AUR and is a newer alternative to xmove. I'm not sure how it fairs as far as application compatibility goes, but it certainly has more features, including the ability to move sessions across ssh tunnels and back. We should probably add this to the page. Does anyone have an example of an application that doesn't work with xmove? It would be interesting to test that with xpra from AUR and see if there's a difference. [[User:Bobpaul|Bobpaul]] 21:10, 14 February 2012 (EST)
+
Connecting to a remove host via ssh:
:You can mention it in the article as an alternative method and see if somebody gives some feedback in this talk page. -- [[User:Kynikos|Kynikos]] 11:14, 16 February 2012 (EST)
+
I cannot use nohup cmd & or use the screen plus Ctrl-A Ctrl-D to let a terminal program running ...
::I added xpra to the article. It seems it is the easiest alternative to use over ssh and it worked fine when I tested it a bit. --[[User:Krisse7|Krisse7]] ([[User talk:Krisse7|talk]]) 20:08, 10 July 2012 (UTC)
+
Didn't try the tmoux aproach.
 +
Really need help were ...
 +
 
 +
Just tried the tmux approach ... and didn't work.
 +
 
 +
Looks like when I exit the ssh session the screen is also terminated ...
 +
 
 +
Really need help were ...
 +
 
 +
Solved my issue:
 +
A little bit bad config in my system:
 +
I was using both sshd.service and sshd@.service and sshd.service have the feature of terminate session program enable and the service is activated at ssh logout althougt is not activated in login.
 +
 
 +
Sorry for the trouble. I hope that this experience will result in a good way to found out the correct method to perform remote executions properly.

Latest revision as of 16:39, 25 November 2013

Cannot use this feature: Connecting to a remove host via ssh: I cannot use nohup cmd & or use the screen plus Ctrl-A Ctrl-D to let a terminal program running ... Didn't try the tmoux aproach. Really need help were ...

Just tried the tmux approach ... and didn't work.

Looks like when I exit the ssh session the screen is also terminated ...

Really need help were ...

Solved my issue: A little bit bad config in my system: I was using both sshd.service and sshd@.service and sshd.service have the feature of terminate session program enable and the service is activated at ssh logout althougt is not activated in login.

Sorry for the trouble. I hope that this experience will result in a good way to found out the correct method to perform remote executions properly.