You could be lazy and (ab)use File::Temp:
#!/usr/bin/perl use strict; use warnings; use POSIX (); use File::Temp (); my $log = File::Temp->new( UNLINK => 0, DIR => '/the/path/to/your/log/folder/', # isn't this too fancy?! you don't need "nice" file names* ;-) TEMPLATE => POSIX::strftime( 'simplebr_%Y%m%d%H%M%S_XXXX', localti +me ), SUFFIX => '.txt', ); print $log 'foo bar'; close $log;
* I guess your "logs" folder is in fact some kind of (very) poor man's queue. If this is correct, you don't want to *sort* those files on a file name basis because it would be too slow, better use whatever your underlying OS offers you for watching a folder (e.g. Sys::Gamin, Linux::Inotify, SGI::FAM, Win32::ChangeNotify). Anyway, you'll have to take some solid countermeasures in order to avoid trashing your disk. ;-)

In reply to Re: Log Files for CGI Submits by AltBlue
in thread Log Files for CGI Submits by Anonymous Monk

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.