From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Lezcano Subject: Re: [PATCH] liblxc: handle interruption/failure of lxc-debian more gracefully Date: Thu, 05 Feb 2009 13:05:03 +0100 Message-ID: <498AD5EF.5040501@free.fr> References: <1233825739.28338.22.camel@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1233825739.28338.22.camel@localhost> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: Matt Helsley Cc: Containers List-Id: containers.vger.kernel.org Matt Helsley wrote: > If lxc-debian fails or is interrupted during debootstrap then the next > invocation of lxc-debian breaks because it only checks for the existence > of the directory. This forces the user to remove the cache by hand to > retry the create step. > > Let's allow the user to re-run lxc-debian to resume/retry. Store the > cache in a partial-$ARCH directory until debootstrap succeeds. Then move > the valid cache to its final destination. > > Signed-off-by: Matt Helsley > That is definitively better ! Applied, thanks. -- Daniel