Christian Hesse <l...@eworm.de> on Mon, 23 May 2011 20:51:17 +0200: > Hello everybody, > > I've installed systemd on my system. Systemd manages processes in > cgroups, so it is able to terminate a process hierarchy if the daemon > or session exits. > > Now this breaks tmux: A user logs in, starts a tmux session, and > detaches it. When the user logs out the tmux session is killed as it > belongs to the same cgroup. > > I think the best way to fix the problem is pam support. There's a pam > module pam_systemd which registers user sessions in the systemd > control group hierarchy. > This could also enable things like pam_limits for tmux. > > Or is there any problem with this? Any comments?
Ok, I found a solution that works fine for me... I have a script that creates a new cgroup via libcgroup [0] and launches tmux within this cgroup. If anybody is interested please take a look at my Arch package [1]. [0] http://libcg.sf.net/ [1] http://arch.lugor.de/eworm/x86_64/tmux-cgroup-0.0.2-1-any.pkg.tar.xz -- Schoene Gruesse Chris ------------------------------------------------------------------------------ Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Data protection magic? Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev _______________________________________________ tmux-users mailing list tmux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tmux-users
