From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Jackson Subject: Re: [PATCH v3 2/5] libxl: add libxl__xs_path_cleanup Date: Mon, 23 Apr 2012 17:49:35 +0100 Message-ID: <20373.34847.574893.779560@mariner.uk.xensource.com> References: <1334928211-29856-1-git-send-email-roger.pau@citrix.com> <1334928211-29856-3-git-send-email-roger.pau@citrix.com> <20373.30292.162693.913028@mariner.uk.xensource.com> <4F957872.3080502@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <4F957872.3080502@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Roger Pau Monne Cc: "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org Roger Pau Monne writes ("Re: [Xen-devel] [PATCH v3 2/5] libxl: add libxl__x= s_path_cleanup"): > Ian Jackson escribi=F3: > > With the C xenstored, the RM command will delete a whole directory > > tree, regardless of its contents. This is documented in > > docs/misc/xenstore.txt. > = > This is a recursive delete, from top to bottom, let me put an example = > which will make this clear, since probably the title is wrong. Imagine = > you have the following xenstore entry: > = > /foo/bar/baz =3D 123 > = > If you do a: > = > xenstore-rm /foo/bar/baz > = > the following will remain in xenstore: > = > /foo/bar > = > What this function does is clean empty folders that contained the = > deleted entry, so using this function on /foo/bar/baz would have cleaned = > the whole directory. Oh! This was quite unclear to me and I didn't read your code closely enough to spot this. I'll go back and read your patch again. Ian.