myocom: Excellent! (And I thought I had batch files cold.) ;-)
Thanks for reminding me that there's always more to learn.
Blue: Good point. Initially, I wanted to maintain a single batch file, if possible. After continued reflection, this looks like a case where two one-line batch files are easier to understand after the development fit. Any maintenance difficulties could be easily handled with documentation (comments in the batch files). (Which is a nice way of saying, it would help me remember what I was trying to accomplish when I looked at those files later.)
Anyone have thoughts regarding the utility of unlinking the log files before the system call? Good idea? Bad idea? No matter?
--f
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.