On 02/09/2013 12:41 AM, Serge Hallyn wrote: > > Not to users who are already scripting around lxc-destroy and would > now have to change all the callers.
I see that and you're absolutely right. Me and other people use stop-destroy-create-start circle as a workaround because there is no other way to modify a container configuration (we wrote about that in this and other threads). > Seriously, 'lxc-destroy' is a vicious enough sounding name, and I > don't like they idea of saying "well other suites use their terms > differently so we have to follow suit." Correct, no objection. >> Or just suggest a way to modify containers configuration. > > Sorry, can you elaborate? You can modify configuration using the > API (in C, python, or, iiuc, lua). You can edit the configuration > file by hand... If there is more you'd like, please do propose it, > sounds interesting. Right now when the configuration file is modified, the container has to be recreated to take it effect. Restart is not enough. Do I (we) miss something? Thanks, tamas ------------------------------------------------------------------------------ Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb _______________________________________________ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
