I'm currently working on a shell script package for remote
administration, involving tmux [1]. A script called tmux-job moves
windows to another session after the contained job has finished (based
on exit code). It must make sure that the target session exists. To
avoid hacking, it would be very practical if there were persistent
sessions (sessions which are not destroyed when the last window has
gone).
I've already digged into the code, but simply not destroying the session
results in server crashes (as expected). Proper patching probably
requires proficiency with the RB tree macros and more.
Is it possible to implement persistent sessions? I can't really estimate
how complex this is. At least, it involves adding an option (set
destroy-empty [on | off]) and something like a dummy pty ("(empty
session)") with no job running inside for empty sessions.
If nobody is interested, but somebody can give me a rough sketch on
where the important places in the code are, I don't mind having another
try myself.
Have a nice day
Jens Stimpfle
[1] Advertisement: https://github.com/jstimpfle/adminscripts
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
_______________________________________________
tmux-users mailing list
tmux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tmux-users
