Ever have a script that is executing another script and get an error that looks like this?…
/path/stub.ksh[2]: /path/XX/script.ksh: not found [No such file or directory]
Then you make sure that the file does in fact exist, and that you can read it?
So why does it say there’s “No such file or directory”?
Might want to check if the file has Windows line breaks. Easiest way to do that is run the following…
cat -v /path/XX/script.ksh
… and you’ll probably see that your lines end with ^M characters. If so, you have Window’s line breaks and you might want to look into not introducing them in the first place (save in Unix format), or check out the dos2unix command.
Please remember to subscribe to the newsletter to stay up to date!You or someone you know looking to buy or sell?
Disclaimer: Thoughts and opinions are my own, and do not reflect the views of any employer, family member, friend, or anyone else. Some links may be affiliate links, but I don't link to anything I don't use myself. You would think this should be self evident these days, but apparently not...