Why not just run --lint on the downloaded file and then check the exit
status of the command? If it's non-zero, then you know there was an error.
Victor
Jack L. Stone wrote:
Chris: I made a few little changes to your script to have it use a "tmp"
file, then ask is the --lint was okay to go forwa
Chris: I made a few little changes to your script to have it use a "tmp"
file, then ask is the --lint was okay to go forward. Only problem, it's not
suitable for unattended updates via cron because of the lint check and
interactive "yes" need to go ahead. If no "yes" within 30 sec, it quits.
Needs