Serge E. Hallyn wrote: > Quoting Cedric Le Goater (clg@xxxxxxxxxx): >> This patchset is a prototype using the container infrastructure and >> the swsusp freezer to freeze a group of tasks. >> >> 2 files are defined by the freezer subsystem in the container >> filesystem : >> >> * "freezer.freeze" >> >> writing 1 will freeze all tasks and 0 unfreeze >> reading will return the status of the freezer >> >> * "freezer.kill" >> >> writing <n> will send signal number <n> to all tasks >> >> * Usage : >> >> # mkdir /containers/freezer >> # mount -t container -ofreezer freezer /containers/freezer >> # mkdir /containers/freezer/0 >> # echo $some_pid > /containers/freezer/0/tasks > > I'd like to point out that by composing this with the nsproxy subsystem > (which I've done and tested), you can > > mount -t container -ons,freezer nsproxy /containers/freezer > > Then you get a new freezer subsystem automatically for every unshare > that you do, avoiding the need to to manually do > > echo $some_pid > /containers/freezer/0/tasks I guess that's true for any subsystem. right ? C. _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers
