Review of "Xpra Session Manager" version 1

Details Page Preview

This extension is meant to enable easy management of Xpra sessions. (See: http://xpra.org/) There are 3 files that you might need to configure in the extension directory: $EXTENSION_DIR/xpra_session_manager@paul.unnsvc.com/attach-detach.sh $EXTENSION_DIR/xpra_session_manager@paul.unnsvc.com/start-stop-server.sh and $EXTENSION_DIR/xpra_session_manager@paul.unnsvc.com/targets.lst == attach-detach.sh This file needs to be executable, so if it lost its execute but during the transfer of the extension, then chmod +x it. It will be executed to attach to targets listed in targets.lst == start-stop-server.sh This file also needs to be executable, so check it before using the extension. In it you will find the command to start/stop the Xpra Xorg server. The provided configuration uses Xdummy, otherwise you can edit the command. If you remove this file then "Start server" won't show up in the menu. == targets.lst Here you need to list the targets you will want to attach to. One target on each line. It won't be reloaded automatically after editing it so you need to reload gnome-shell after editing it (Alt+F2 and type "r", and enter). When adding remote targets, such as "ssh:example.com:1000", make sure to have passwordless ssh authentication enabled on the server. When executing the server or attaching to a session, this version won't keep track of which processes are active (Partly due to xpra not listing "attached" sessions, and partly because there doesn't seem to be a way of checking return status when executing a binary from javascript. But I might fix this in a later version with using PID files in the shell scripts), so don't click the menu items too fast or its state will be out of sync with the actual state of running processes. Leave a comment if there's something wrong and I'll try to fix it.


No comments.

FAQ

Files

Note: Binary files aren't shown on the web site. To see all files, please download the extension zipfile.

All Versions

Version Status
1 Rejected

Previous Reviews on this Version

nzjrs posted a review
Why are you using the trySpawnCommandLine function? Is there any reason you can't call GLib.spawn_async directly? It has the benefit of giving you the PID back so you can track if it is still running etc
paul@unnservice.com posted a review
I'm not familiar with the gnome-shell Javascript API yet, I'll fix it with GLib.spawn_async.
nzjrs posted a review
By the way, this is the GLib API http://developer.gnome.org/glib/stable/glib-Spawning-Processes.html Unfortunately you might need to do some guesswork and grepping to see how it maps to javascript.
gcampax rejected
Putting on hold, waiting for the newer version using GLib.spawn API