Although other monks have pointed out why it will be next to impossible to answer your questions, I will take a pre-caffeine stab in the dark and guess that the script's working directory is different when run under the scheduler than it is when run from the command line. Thus, perhaps it is "Searching..." for a file because it is looking in the wrong directory. Of course, it could be "Searching..." for Mr. Goodbar for all I know. | [reply] |
john7701,
Have you looked at the parts of the script that outputs text to the screen?
You have not posted any code for anyone to help you with.
Please read How do I post a question effectively? if you have not already done so.
Martin
| [reply] |
We can hardly recognize the output of a program we don't know. Did you write that script yourself? Evidence suggests that the answer is "no". If so, then PM is for discussing Perl, not stuff that happens to be written in Perl. If you have some code to show, like a relevant portion of the program under consideration, I bet someone may help you.
| [reply] |
The script is my own. I am not new to Perl and am aware of redirection and do so when needed.
This output is not from my own code. I assume it is from some library module that I hoped someone could recognize. I am using a grep call to filter an array on a regex.
The interesting thing is that when running in command line I can see flashes of the word "searching" that dissappear. The scheduler seems to be able to capture those suppressed messages. | [reply] |
| [reply] |
| [reply]
[d/l] |
Thanks. It was worth a shot to see if others recognize the output text. | [reply] |