lindsay@cheviot.UUCP (02/25/87)
The problem we were having was caused by the presence of #! lines at the start of shell scripts. cron does a "sh -c" of the command line in crontab and the version of the shell used does not recognise # as a comment line so bombs out on any shellscript in the file that starts with #!..... Thanks to Nigel Horne (njh@root44.uucp for putting me on the track of that one. Lindsay