Hi Gene!
Anno domini 2019 Mon, 11 Mar 07:49:50 -0400 Gene Heskett scripsit:
On Monday 11 March 2019 04:49:49 Dr. Nikolaus Klepp wrote:
Anno domini 2019 Sun, 10 Mar 11:56:17 -0500
Michael scripsit:
On Sunday 10 March 2019 11:02:50 am Gene Heskett wrote:
On Sunday 10 March 2019 11:35:32 BorgLabs - Kate Draven wrote:
On Sunday 10 March 2019, J Leslie Turriff wrote:
Is there a way to make TDE aware of running non-Trinity applications so that they can be resurrected after Logout/Login? I have at least one X11-based application (X2 - The Programmer's Editor) that I use extensively, and it would be nice if it could remember across Logout/Login events. I'm wondering if something like a DCOP wrapper might do the job?
Leslie
Load the application into your autostart dir. /home/foo/.trinity/autostart Also, check the program's setting to see if it has an autostart feature.
Kate
Hi Kate; I have some stuff in that caregory, and since I'm the only (sorta human) user, I've found a start stanza for such in /etc/rc.local works well if it doesn't need a login. And since I setup ssh-keys, all that stuff now works well after a fresh boot. So all my other machines that are alive, are mounted to /sshnet at a reboot without my having to remember 4 to 6 of those commands to do by hand each time.
Gene, Kate,
Would either of these work for launching several of these types of Konsole commands like (using keys for login):
ssh "$PORT" -L 11111:$IP:25 -L 22222:$IP:110 "$ACCOUNT@$IP"
at TDE login?
Sure it works. But you have to make sure that you kill the ssh instance when logging out of TDE :-)
I am not, at least consciously. Is that why a logout here is a full hot reboot?
That logout behaviour can be configured somewhere in tcontrol (I have mine to just fhut down the machine and don't ask me again). The problem with the ssh example is that when user A logs out and ssh is not closed, and a user B logs in, then B still has the portredirection of A in place ... which could lead to funny helpdesk calls, 'cause the cure number 1 aka "reboot" will seamingly fix the problem for user B ... till user A wants to log in and calls the helpdeskt which tells him to reboot which solves the problem for user A till user B wants to log in and calls ... *sigh* ... things could be so easy if users just were not creative :-)
Nik
Thanks, Michael
- To unsubscribe, e-mail:
trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Cheers, Gene Heskett