well, here's where I'd start: On Thu, Aug 11, 2016 at 7:41 AM, Rich Shepard <[email protected]> wrote:
> A shell script that has worked flawlessly in the past was set to run > using > the 'at' command. And it did run ... I think. > > My inbox received this message: > > Subject: Output from your job 63 > That was job #63, whose run is logged somewhere so you can be sure of which script it is. unfortuantely the queue for at(1) is emptied after the job runs so you can't use a tool like atq(1) to examine what happened. > sh: line 67: mail.list: No such file or directory > this is saying that the 67th line of some script referred to a file that was unavailable at runtime. That's where I'd start looking for a mail.list file reference - and one that does not have a /full/path in front of it, so perhaps a cd to an expected directory failed, and/or the file moved (perhaps temporarily) from where the script typically finds it, or a filesystem was missing at runtime, or a million other reasons... > I tried a Web search for this string but found nothing enlightening. The > file, 'mail.list' does exist and the script referring to it has only 7 > lines, including one blank line. > Seems like some script that ran has at least 67 lines. It could be the case that a subordinate script called from the master script is the one throwing the error message. The shell's built in error reporting is pretty minimal, as you see here :) Please provide me with a clue on how to seek the meaning of this message > and an idea how to determine if the script actually sent the message to the > addresses in mail.list. > Well, I'd check my mail logs to determine that. That error message doesn't specify what was happening with mail.list - perhaps it was *read* successfully, and then the script attempt laters to remove it or add to it and it had vanished in the meantime. Sounds like your processing scripts could use some more error handling (check the shell's last-job-exit-code variable: $? after you do things you care about and explicitly log that status code or a success message). _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
