Are you sure files have changed? cvs outputs only files with a status to STDOUT which you are capturing. All the messages that start with "cvs update: Updating dir/subdir" are written to STDERR. I know you may not want to capture these messages, but perhaps for testing you should capture STDERR as well so you can at least ensure that the cvs is running when you run your script through cron. At least then you know your script is working. You can do this simply by changing: 

 open INFO, "cvs update -dP |"; 
#to
 open INFO, "cvs update -dP 2>&1|";

[download]

I tested your snippet and it seemed to work as advertised.

HTH

In reply to Re: output to a file by pzbagel
in thread output to a file by sachaer

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.