On 19/12/2019 16:22, Celeste Weingartner via shifter-users wrote: > excuse me, the line should have been xpra start ssh://someu...@apphost.com > --start-child='google-chrome' -- > Im not sure how to A) track who's got what session and be able to reattach > to an already running one.. If a single session already exists, running "xpra version" will return 0. > or B) limit spawinng of xsessions to 1. As per previous email, you could derive the X11 display from the userid. > and finally C) handle a session that dies, hangs, or crashes, by starting a > new one. If a session dies, you can just start a new one. This is no different from not having a session to begin with. Session hangs are very rare, but if a server exists and is not responding then you may have to kill it. If a server has crashed, starting a new one with the same display number will fail. You can recover that display by running the xpra server with "--use-display".
Thinking some more about the new subcommands, I think that this would be much clearer and cover everything: "xpra upgrade-or-start --use-display=auto" This would "xpra upgrade" the server if one is found, otherwise start a new one and recover an existing display if it is found. Here's a ticket: https://xpra.org/trac/ticket/2523 Cheers, Antoine > > On Thu, Dec 19, 2019 at 2:19 AM Celeste Weingartner < > celeste.weingart...@gmail.com> wrote: > >> im writing a frontend for Xpra that will use ssh to connect. I would like >> to make a ultra persistant chrome session be remotely served.. Ive got >> firejail working for chrome, and i can manually connect with xpra start >> someu...@apphost.com --start-child='google-chrome' and that works.. and i >> can reattach to it no problem but if i reisssue another start, it starts >> another x session, which i do not want.. I want it limited to one per user. >> max. >> >> >> On Mon, Dec 16, 2019 at 6:06 AM Antoine Martin via shifter-users < >> shifter-users@lists.devloop.org.uk> wrote: >> >>> On 16/12/2019 07:59, Celeste Weingartner via shifter-users wrote: >>>> Hi Everyone, im not sure if the devel list would be the place for this >>> or >>>> not.. So i'll ask. >>>> >>>> Im trying to use Xpra to create an application server. For a specific >>>> application. I do not want users to be able to spawn more than 1 xpra >>>> server process. I want them to be limited to 1. Short of disabling >>> server >>>> commands, and using firejail which im already doing, how can I further >>>> limit it to one server per user? Im willing to be there's some sort of >>>> bash magic that can be done in the xpra startup, but im unsure where to >>>> even begin there, im not a python coder... Bash I can do.. But can >>> anyone >>>> provide some pointers or tips? >>> How are you going to start the sessions? Is it going to be on demand for >>> each user? >>> How are they connecting to the server? ssh? >>> Are you going to give them a command line to run or an xpra URI they >>> just click on? >>> >>> This is not the first time something like this has been requested, so >>> maybe we can make it easier to setup. >>> >>> Cheers, >>> Antoine >>> >>>> >>>> Thanks in advance, >>>> >>>> Celeste >>>> _______________________________________________ >>>> shifter-users mailing list >>>> shifter-users@lists.devloop.org.uk >>>> https://lists.devloop.org.uk/mailman/listinfo/shifter-users >>>> >>> >>> _______________________________________________ >>> shifter-users mailing list >>> shifter-users@lists.devloop.org.uk >>> https://lists.devloop.org.uk/mailman/listinfo/shifter-users >>> >> > _______________________________________________ > shifter-users mailing list > shifter-users@lists.devloop.org.uk > https://lists.devloop.org.uk/mailman/listinfo/shifter-users > _______________________________________________ shifter-users mailing list shifter-users@lists.devloop.org.uk https://lists.devloop.org.uk/mailman/listinfo/shifter-users
