Jo for lists and groups wrote:
Thanks for your time, John.
You solved the mystery! :)
You're welcome. :-)
Now I shall resolve my problem!
As for that open to fork a child, I got that from Perl Cookbook 19.6 and
echoed by a couple of other sources as I spent days looking and learning
about ways to minimize security risks with issuing system commands. Do you
disagree with that method? It looks like I am certainly missing knowledge
about exiting child processes and/or returning control to the parent
process? Of course, I worked on the backup as its own script in isolation
and it worked. It only caused a problem when integrated with other stuff.
From what you are doing it looks like you don't need to fork a child
process at all.
Anyone with suggestions for further reading to learn about those aspects?
Have you read:
I'll drop the quotes, but probably continue like
rename ($newFile, $petFile);
Because I find grouping the arguments makes it easier to read.
You should also read the FAQ:
perldoc -q quoting
My full script does include more insightful error messages in its test mode.
Thank you for your comments on the rest; always something new to learn! :)
Those people who think they know everything are a great
annoyance to those of us who do. -- Isaac Asimov