Apologies if this has been mentioned elsewhere, my search skills may be lacking somewhat today.
I have a script that does the following (as a test):
Code:
find . -name "*.txt" -exec file {} \; >>$sFullFilePath
Now, the variable is set up up correctly in the script too. When I run the script myself, the file pointed at in $sFullFilePath is populated correctly.
However, when this is run using crontab on the identical directory (debug code proves this), it just creates an empty file.
When I look at the stack, it doesn't mention the output. Is crontab treating it as 2 seperate lines? The script starts with #!/bin/bash, so why should it act differently?
<is confused>
