Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!mit-eddie!uw-beaver!tektronix!sequent!djg From: djg@sequent.UUCP (Derek Godfrey) Newsgroups: comp.unix.wizards Subject: Re: BSD:sockets::SVID:(what?) Summary: VMIN/VTIME Message-ID: <3475@sequent.UUCP> Date: 5 Jul 88 16:17:19 GMT References: <5968@umn-cs.cs.umn.edu> <2820@ttidca.TTI.COM> <58603@sun.uucp> Organization: Sequent Computer Systems, Beaverton, OR Lines: 13 In article <58603@sun.uucp>, guy@gorodish.Sun.COM (Guy Harris) writes: > > I don't see why the streams mechanism itself would have to be changed. > > Can you say "VMIN/VTIME"? I thought you could.... However, you can't say it > on a vanilla S5R3.1 system, at least not if your tty driver is streams-based > (which the S5R3.1 one isn't). This requires a small change in strwrite() and a distinquishable message from the tty module. (the problem is in VTIME>0 VMIN=0 - the timoute must be invoked from the requesting code (strwrite()) not the line displine which may not even be called) Also note that any new TCXXX style ioctl also needs to have corresponding code in strioctl (size and direction information has to be hard coded). However I would not call these `changes to the mechanism'.