Monksters,

I've been trying to write something to archive the files I'm processing and came up with this:

foreach $year (@years) { foreach $month (@months) { foreach $day (@days) { @filelist = glob("/home/reports/ftp/WSB/*$year$month$day*"); $filecount = @filelist; print "$month-$day $hour:$filecount\n"; $gzname = $month.$day.".gz"; foreach $filename (@filelist) { `cat $filename|gzip -9 >>$gzname`; `rm $filename`; } } @days = @alldays; } }
I don't like this because, its an after the fact clean up and I'd like to archive each file as I process it, It creates one monolith file and I've had some issues with gzip later claiming that these files are corrupt.

I tend to use gxip because thats what the people who taugh me Unix used. Are any of the others more reliable? I'd like to have them behave like they were tarred then zipped and I looked at some of the modules on cpan and it didn't look like any of them worked without going through the whole process of unzipping the whole archive, adding the new file to the tar and then rezipping. This seemed very expensive to me. I supposed taring isn't important if the files remain atomic when I uncompress the archive.

Anyhow, sorry to be asking so many newbie questions...

A hopeful Jimbus asks, "Never moon a werewolf?"

In reply to Whats a good process for archiving cron processed files? by jimbus

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.