| commit | 4a8bdc9ac050e613f573687317bedf4f84dae111 | [log] [download] |
|---|---|---|
| author | Kir Kolyshkin <kir@openvz.org> | Sat Nov 24 05:22:43 2012 +0400 |
| committer | Kir Kolyshkin <kir@openvz.org> | Sat Nov 24 05:36:24 2012 +0400 |
| tree | bfb2d3cf084b697441af039ca8b31605f6b09705 | |
| parent | b1f654cc755d6e02c94834abc37eb578b55a0add [diff] |
vzctl create: allow existing empty VE_PRIVATE Previously, vzctl create checked if a directory for future CT's private area exists -- and if it is, CT creation fails. Apparently, it is problematic for some setups, when the directory used for VE_PRIVATE must already be there. Let's loose the check a but and allow for existing empty directory. http://bugzilla.openvz.org/2450 Reported-by: Andrew Kornilov <akornilov@gmail.com> Signed-off-by: Kir Kolyshkin <kir@openvz.org>