One possibility is to (somehow) make each release use hardlinks from the last. I'm not sure how to do that consistently across versions, though, and that wouldn't make it fast, just not quite as slow.
But yes, it does depend on the filesystem, and some are actually slower at unlink() calls than others. I do actually make it automatically execute after a deploy, because each one is going to take as long as any other, so better to feel the pain in small doses than all at once. On Mon, Apr 28, 2008 at 8:37 AM, Jamis Buck <[EMAIL PROTECTED]> wrote: > It depends on the filesystem. On our FreeBSD systems, cleaning up even > just a handful of old releases can take (as you said) forever, but on our > linux boxes the deletes go significantly faster. > > If anyone knows a faster way for deleting subtrees, I'm all ears, because > the speed of deletion is the only thing that is keeping me from making > deploy:cleanup automatically execute after a deploy. > > - Jamis > > > On Apr 28, 2008, at 6:16 AM, Rob Sanheim wrote: > > > > 2008/4/25 Rafael G. <[EMAIL PROTECTED]>: > > > > > Josh Schairbaum escribió: > > > > > > > > > > You can set the number of releases to keep, but you'll have to look > > > > in > > > > the docs for the variable name, I can't remember. > > > > > > > > > > > > I remember :) > > > > > > set :keep_releases, 4 > > > > > > regards! > > > > > > > > As an aside, does anyone else notice that the deletion seems to take > > forever? I thought a rm -rf would be pretty fast, even if there is a > > lot of cruft in each release directory? > > > > - Rob > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
