From: beto@plan9.cs.su.oz.au beto@plan9.cs.su.oz.au
Subject: Panel + forks + postnote
Date: Mon, 16 Oct 1995 18:31:51 -0400 [thread overview]
Message-ID: <19951016223151.UXMExT8KaOhj_rwEg8LgQxuhCd2tr7b530AsvuHcx-k@z> (raw)
In <95Oct13.094213edt.78814@colossus.cse.psu.edu>
td@plan9.att.com wrote:
> plan9.cs.su.oz.au!beto asks:
> >I'm having problems after killing processes with
> >the panel library. It looks like there is some kind of
> >sincronization program, I'm not quite sure what's going on.
> >The error is
> > bitblt: bad slave 32 on event pipe: fd out of
> > range or not open
>
> I believe the problem is that when you execute
> postnote(PNGROUP, getpid(), "kill\n");
> after having done
> einit(Emouse);
> that you're killing the process that's reading the
> mouse. Ironically, this postnote appears not to
> terminate the processes that you started by calling
> filter. At least, it didn't work when I tried it on
> my nextstation.
>
forsyth@plan9.cs.york.ac.uk pointed out the einit's process, so I just put the
child process created in filter in a different note group, then
did a postnote PNGROUP of that. That works fine.
Thanks a lot
next reply other threads:[~1995-10-16 22:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-10-16 22:31 beto [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-10-13 19:29 beto
1995-10-13 13:27 td
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=19951016223151.UXMExT8KaOhj_rwEg8LgQxuhCd2tr7b530AsvuHcx-k@z \
--to=beto@plan9.cs.su.oz.au \
/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.
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).