Re: [PLUG] Shell script error explanation needed

On Thu, 11 Aug 2016, Steve Dum wrote: > Thus the earlier recommentation to use a full paths in the script so you > don't have to be in a particular directory when submitting the at job. Steve, Done. Thanks, Rich ___ PLUG mailing list

Re: [PLUG] Shell script error explanation needed

On Thu, 11 Aug 2016, Steve Dum wrote: > a ~ based path only works if you were cd'ed to your home directory when > you submitted the script with at. Steve, Ah, that explains it. If I correctly recall what I did in the past, I was in my home directory when I created the at jobs. > if you were

Re: [PLUG] Shell script error explanation needed

Rich Shepard wrote: > >> I suspect the required facts to explain the failure are >> 1. what directory is the real mail.list file in? >> 2. what directory are you in when you submit the at job? > While this does not make sense to me since I provided the full path > relative to ~/ (including

Re: [PLUG] Shell script error explanation needed

On Thu, 11 Aug 2016, Steve Dum wrote: > To answer your question about how the error can be at line 67 when the > script only has 5 lines, realize that at adds a bunch of stuff at the top > of the script Steve, OK. > I suspect the required facts to explain the failure are > 1. what directory

Re: [PLUG] Shell script error explanation needed

To answer your question about how the error can be at line 67 when the script only has 5 lines, realize that at adds a bunch of stuff at the top of the script - from the man page of the at on my machine: The working directory, the environment (except for the variables BASH_VERSINFO,

Re: [PLUG] Shell script error explanation needed

On Thu, 11 Aug 2016, chris (fool) mccraw wrote: > Be that as it may, the shell script would have said "/path/to/mail.list - > file not found" if it was *using* that full path, so you are still (IMHO) > looking for an unqualified pathname use. The test script ran correctly. test-1.sh:

Re: [PLUG] Shell script error explanation needed

On Thu, 11 Aug 2016, chris (fool) mccraw wrote: > Be that as it may, the shell script would have said "/path/to/mail.list - > file not found" if it was *using* that full path, so you are still (IMHO) > looking for an unqualified pathname use. Chris, I'm thinking that I might have not put the

Re: [PLUG] Shell script error explanation needed

On Thu, Aug 11, 2016 at 8:25 AM, Rich Shepard wrote: > >I passed at the full pathname to the script just as I've done before. Be that as it may, the shell script would have said "/path/to/mail.list - file not found" if it was *using* that full path, so you are

Re: [PLUG] Shell script error explanation needed

On Thu, 11 Aug 2016, chris (fool) mccraw wrote: > well, here's where I'd start: >> 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

Re: [PLUG] Shell script error explanation needed

On Thu, 11 Aug 2016, David Gibbons wrote: > Does it ruin when you run it manually? I'll set up a test mail.list and see. > Jobs run from at or from have a pretty limited environment and won't > necessarily have everything your shell does. it's possibly that 'at' ram > your script from an

Re: [PLUG] Shell script error explanation needed

well, here's where I'd start: On Thu, Aug 11, 2016 at 7:41 AM, Rich Shepard 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:

[PLUG] Shell script error explanation needed

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 sh: line 67: mail.list: No such file or directory I tried a Web search for this string but