in reply to
Re: Re: file handling question
in thread file handling question
I think that confirms that my choice for IO::AtomicFile is a good one ;-)
The second part, which I can see was a little confusing, is as follows: (I am on win32, but want to be portable)
I have a server process and it often needs to read config files for instructions. I expect the file to always be readable, but one time it wasn't (I think I was in the debugger and maybe viewing the file also, no locking that I am aware of...). Instead of just throwing out the job, I figured I could retry opening the file a few times, maybe sleeping .1 sec in between? Is this just overkill?
Curious, if you are manually editing a crontab file in vi and cron runs, what happens? (I don't have unix or cron...just use windows and we don't expect users to edit config files behind our backs ;-)
thanks for any defensive programming ideas !