From: Andrej Borsenkow <Andrej.Borsenkow@mow.siemens.ru>
To: Bart Schaefer <schaefer@candle.brasslantern.com>
Cc: <zsh-workers@sunsite.dk>
Subject: Re: Setting MONITOR after startup
Date: Mon, 26 Mar 2001 11:52:17 +0400 (MSD) [thread overview]
Message-ID: <Pine.SV4.4.33.0103261149430.13167-100000@itsrm2.mow.siemens.ru> (raw)
In-Reply-To: <1010325235757.ZM11718@candle.brasslantern.com>
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
-------------------------------------------------------------------------
prev parent reply other threads:[~2001-03-26 7:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-25 23:57 Bart Schaefer
2001-03-26 7:52 ` Andrej Borsenkow [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.SV4.4.33.0103261149430.13167-100000@itsrm2.mow.siemens.ru \
--to=andrej.borsenkow@mow.siemens.ru \
--cc=schaefer@candle.brasslantern.com \
--cc=zsh-workers@sunsite.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).