Path: utzoo!utgpu!water!watmath!uunet!labrea!bloom-beacon!tut.cis.ohio-state.edu!mailrus!ames!zorch!pacbell!gladys!skeeve!islenet!uhccux!richard From: richard@uhccux.uhcc.hawaii.edu (Richard Foulk) Newsgroups: unix-pc.bugs Subject: Re: Bug report--window driver 3.51 bogosity during window switch Keywords: bogus input flushing and signal sending Message-ID: <2416@uhccux.uhcc.hawaii.edu> Date: 24 Sep 88 11:24:35 GMT References: <10552@stb.UUCP> <761@rush.cts.com> <10581@stb.UUCP> <4789@cbmvax.UUCP> <4805@cbmvax.UUCP> Reply-To: richard@uhccux.UUCP (Richard Foulk) Organization: University of Hawaii Lines: 12 } Perhaps it should be considered a bug in the Unix PC's system() function, } since SIGWIND is a legitimate process-group-type signal that might occur, } but system() only takes care of SIGINT and SIGQUIT. The system(3) library function wasn't ever intended to cover all eventualities. It was meant to be small and simple. Most fair-sized screen-oriented programs I've seen use their own version of it. There are just too many details that are dependant on the programs approach to signal handling, process control, etc. Richard