in reply to Re: File::Find in a thread safe fashion
in thread File::Find in a thread safe fashion

Thanks, I'll look into those.

My needs are _loosely_ what a 'du' does, but a little more complicated - I'm needing (assuming a tree of):

/usr                       10mb
    /local                  5mb 
          /apache           5mb
    /include                1mb
    /system                 1mb

[download]
followed by a little hackery to assign different 'structures' to cost centres.

So yes, doing a du of /usr, then of /usr/local, then of /usr/local/apache, would be a solution, but then I'd end up reading the tree lots of times, which'd get very expensive.

Replies are listed 'Best First'.
Re^3: File::Find in a thread safe fashion
by Moron (Curate) on Jul 28, 2006 at 12:52 UTC
    If each such 'structure' could be put in a separate device partition, either directly or probably handier using symbolic links to isolate it from where it normally lives, then Filesys:Df would still do the job more efficiently than having to recalculate the (f)statvfs yourself.

    Update: The way my own hosting supplier does it is to have a separate partition per client, symbolically link the top directory of each website structure as a subdirectory of where the apache server is installed and alias each website to that directory in the httpd.conf. They have a different location for all the webmail though, just because that has a different tariff per MB.

    I imagine there is a downside that they have to automate partition allocation and it is hard for customers to give up disk space they have requested because extending partitions is significantly easier than recycling part of an allocated partition, even more so if this has to be automated.

    -M

    Free your mind

[reply]

In Section Seekers of Perl Wisdom