If indeed the only change is the OS, then I see a couple of places to go look:
- You no longer have the proper permissions to write the new log file (which, in fact is what your error messages says!)
- Some Process has the log open and has not been properly fitted out with 'close and re-open on my signal' logic.
- This being Windows, trying to read a file that someone else has open for writing can be problematic (see the previous bullets)
- Your old system was taking advantage of a 'Windows Quirk' (I have been told to stop calling them (adjective) Windows Bugs). That 'quirk' has been patched in the new OS.
- And, the ever popular solution -- "Murphy hates you"
If it was me, I'd start with the Permissions issue first.
Good luck, this is likely not to be the first 'OS quirk' issue you are going to run into. (Ask me sometime why I hate upgrading Operating Systems. Preferably sometime when we both have a stein of beer at hand and the night is young....)
----
I Go Back to Sleep, Now.
OGB
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.