Chet Ramey wrote:
> Com MN PG P E B Consultant 3 wrote:
> > monitest.sh: line 9: 3486 Terminatedtail -f foo >bar
> > (1) Monitor was not set
>...
> Not really. If a pipeline in a shell script is killed by a
> signal other than SIGINT or SIGPIPE, the shell reports it. People
> generally want
Com MN PG P E B Consultant 3 wrote:
> monitest.sh: line 9: 3486 Terminatedtail -f foo >bar
> finish
>
>
>>From this we can see:
>
> (1) Monitor was not set
> (2) Even if it had been set, +m would have turned it off
> (3) Still, the Terminated message is printed.
>
> Strange, isn't it?
No
> Com MN PG P E B Consultant 3 wrote:
> > (PID) Terminated tail -f file >outfile
> > Is there a way to suppress this message? (bash 2.05b)
>
> Use:
> set +m
> Why is monitor set for your script? That would only be typical for
> interactive shells but not typical for scripts.
G
Com MN PG P E B Consultant 3 wrote:
> (PID) Terminated tail -f file >outfile
> Is there a way to suppress this message? (bash 2.05b)
Use:
set +m
Or:
set +o monitor
-m Monitor mode. Job control is enabled. This option is
on by default for i
