Cameron Simpson <[EMAIL PROTECTED]> writes:
[...]
> Pretty much only things explicitly opening /dev/tty.
>
> You may also get it if some clueless piece of code assumes it's talking
> to a tty and does a stty or something like that.
I've written many cluesless pieces of code..But missed this on
On Tue, Apr 03, 2001 at 09:25:26AM -0700, Harry Putnam <[EMAIL PROTECTED]> wrote:
| > Another possibility is that your script is dependent upon running on
| > a terminal. Cron jobs do not have a controlling terminal, nor do they
| > have a tty attached to any inputs or outputs.
|
| What kind of t
Cameron Simpson <[EMAIL PROTECTED]> writes:
> Another possibility is that your script is dependent upon running on
> a terminal. Cron jobs do not have a controlling terminal, nor do they
> have a tty attached to any inputs or outputs.
What kind of things would do that. Do you mean something lik
On Mon, Apr 02, 2001 at 10:58:23PM -0700, Harry Putnam <[EMAIL PROTECTED]> wrote:
| I'm getting an error message from a shell script that has been working
| for a long time. Tinkered with it and now get an error message I
| don't understand.
| I'm not going to post the whole script, its a bit lon
I'm getting an error message from a shell script that has been working
for a long time. Tinkered with it and now get an error message I
don't understand.
I'm not going to post the whole script, its a bit long and I know this
works when run from the command line. However when run from cron I
ge
