Ticket URL: http://code.x2go.org/horde4/whups/ticket/?id=57 ------------------------------------------------------------------------------ Ticket | 57 Created By | dick.kniep@lindix.nl Summary | second time start-on-connect does not work Queue | pyhoca-gui Version | HEAD Type | Bug State | Unconfirmed Priority | 2. Medium Operating System | 4 Owners | ------------------------------------------------------------------------------ dick.kniep@lindix.nl (2011-03-05 13:49) wrote: Starting with pyhoca-gui with the following line works: pyhoca-gui -P Lindix --start-on-connect works the first time. Then I end the session by ending the called program and try to start again (common situation) result othing happens. Expected is that the program starts.
Ticket URL: http://code.x2go.org/horde4/whups/ticket/?id=57 ------------------------------------------------------------------------------ Ticket | 57 Updated By | Mike Gabriel <mike.gabriel@das-netzwerkteam.de> Summary | second time start-on-connect does not work Queue | pyhoca-gui Version | HEAD Type | Bug -State | Unconfirmed +State | Not A Bug Priority | 2. Medium Operating System | 4 -Owners | +Owners | Mike Gabriel ------------------------------------------------------------------------------ Mike Gabriel <mike.gabriel@das-netzwerkteam.de> (2011-03-07 18:46) wrote: Please refer to the PyHoca-GUI man page, esp. this section: <snip> --start-on-connect Start a session directly after authentication (only if no suspended sessions are available). --resume-on-connect, --resume-newest-on-connect After authentication directly auto-resume the newest available running/suspended session. --resume-oldest-on-connect After authentication directly auto-resume the oldest available running/suspended session. --resume-all-on-connect After authentication directly auto-resume all available running/suspended session. </snip> To gain the functionality you want: use these two options: pyhoca-gui --start-on-connect --resume-on-connect -P <profile_name> However, these options are still not very well tested. If you encounter more problems, please open a new bug ticket for them that explains exactly the new problem. I consider this bug as closed (i.e. as ,,Not A Bug'').
-
bugs＠x2go.org