* Setting MONITOR after startup
@ 2001-03-25 23:57 Bart Schaefer
2001-03-26 7:52 ` Andrej Borsenkow
0 siblings, 1 reply; 2+ messages in thread
From: Bart Schaefer @ 2001-03-25 23:57 UTC (permalink / raw)
To: zsh-workers
While fooling with Ryan Richter's infinite-loop-bug, I happened to try
running `zsh +m':
zagzig% setopt
interactive
norcs
shinstdin
zle
zagzig% setopt monitor
zsh: can't set tty pgrp: operation not permitted
zagzig% setopt monitor
zagzig% sleep 10 &
[1] 11706
zagzig% jobs
[1] + running sleep 10
zagzig%
[1] + done sleep 10
zagzig%
Why did "setopt monitor" fail the first time, but not the second time?
Also, I can't reproduce it now with "zsh -f +m" but at one point the entire
shell got stopped with a SIGTTOU. This led me to notice that there's a lot
of signal handling that's only done when `jobbing' is true when the shell
first starts up; maybe some of that should be independent of `jobbing', or
maybe it all needs to get done again somewhere else if the state of MONITOR
changes?
No patch yet ...
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Setting MONITOR after startup
2001-03-25 23:57 Setting MONITOR after startup Bart Schaefer
@ 2001-03-26 7:52 ` Andrej Borsenkow
0 siblings, 0 replies; 2+ messages in thread
From: Andrej Borsenkow @ 2001-03-26 7:52 UTC (permalink / raw)
To: Bart Schaefer; +Cc: zsh-workers
Actually this is very similar to what happens under Cygwin ("not an owner"
or like this trying to set tty pgrp). This happens only for zpty.
Just in case it may be useful to compare two cases. I am off for this week
so hardly have any chance to do it.
-andrej
On Sun, 25 Mar 2001, Bart Schaefer wrote:
> While fooling with Ryan Richter's infinite-loop-bug, I happened to try
> running `zsh +m':
>
> zagzig% setopt
> interactive
> norcs
> shinstdin
> zle
> zagzig% setopt monitor
> zsh: can't set tty pgrp: operation not permitted
> zagzig% setopt monitor
> zagzig% sleep 10 &
> [1] 11706
> zagzig% jobs
> [1] + running sleep 10
> zagzig%
> [1] + done sleep 10
> zagzig%
>
> Why did "setopt monitor" fail the first time, but not the second time?
>
> Also, I can't reproduce it now with "zsh -f +m" but at one point the entire
> shell got stopped with a SIGTTOU. This led me to notice that there's a lot
> of signal handling that's only done when `jobbing' is true when the shell
> first starts up; maybe some of that should be independent of `jobbing', or
> maybe it all needs to get done again somewhere else if the state of MONITOR
> changes?
>
> No patch yet ...
>
>
--
------------------------------------------------------------------------
Andrej Borsenkow Fax: +7 (095) 737 2747
Siemens ICP ITS Moscow Tel: +7 (095) 737 2723
E-Mail: Andrej.Borsenkow@mow.siemens.ru
-------------------------------------------------------------------------
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2001-03-26 7:52 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-03-25 23:57 Setting MONITOR after startup Bart Schaefer
2001-03-26 7:52 ` Andrej Borsenkow
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).