Opened 15 years ago
Closed 14 years ago
#28 closed enhancement (fixed)
run sessions and their clients with daemonizable threads
Reported by: | Antoine Martin | Owned by: | Antoine Martin |
---|---|---|---|
Priority: | major | Milestone: | 1.0 |
Component: | Client | Keywords: | |
Cc: |
Description
At the moment, xpra supports this on the server: the xpra server stays alive even when shifter_server is stopped.
Ideally, we want to keep all the sessions running and just re-load the session files when the server re-starts. The problem comes from the fact that NX writes to stdout and we watch this output to get the current session state, we will need to redirect to a file instead and watch that (and maybe also start it with 'nohup'?)
Change History (3)
comment:1 Changed 15 years ago by
Summary: | run sessions and their clients with deamonizable threads → run sessions and their clients with daemonizable threads |
---|
comment:2 Changed 14 years ago by
Owner: | changed from Antoine Martin to Antoine Martin |
---|---|
Status: | new → accepted |
comment:3 Changed 14 years ago by
Resolution: | → fixed |
---|---|
Status: | accepted → closed |
The main (large) changeset: r2625
Note: See
TracTickets for help on using
tickets.
mostly done for:
We use a wrapper which prints the pid, we then capture it from the server and store it. When reloading the pids, we ensure they are still valid (and not just another process re-using that pid number) by testing open file descriptors and checking for the log file. Not pretty but it works, we should eventually change that to use standard pid files (ala stop-start-daemon) fairly easily too.
You can now kill the server, restart it and the existing sessions will still be there.