Quote:
Originally Posted by
Paul Walker
Hi thank you for the advice. I am not sure if I am understanding correctly what you mean I don't believe there are any newline characters contained in the target.
The way you posted it made me think of <newline> chars.
Quote:
. . . copy the final .xml file to its final destination on another disk on our network.
Usage of
cp and the host part missing in the target path lends itself to the assumption you have NFS exports mounted? Sure it's correctly mounted?
Quote:
Something does seem not quite right though when I try to copy with the $NOW variable included in the file name I am unable to do so even under the same directory, could the $NOW variable have a time limit on it since it is based on the current time?
Would be helpful to see the $NOW variable, no? There's definitely no time limit on variables. Perhaps there are no files with $NOW?
Quote:
I have included the rest of the code for the script the end product is 4 .xml files
That script is overly complicated and impossible to read and digest.
- Don't run several
sed scripts repeatedly on identical files - make that one script. What are those double single quotes for?
- Don't use lengthy path names - put those into punchy variables.
- Don't pipe text into
cat with a redirected stdout - redirect immediately. What is that single lonely
cat for?
Quote:
Is there a different set of permissions on the ksh?
Definitely not. Permissions are OS / file system features, not shells'.