[Python-checkins] python/dist/src/Doc/lib libos.tex,1.74.2.1.2.8,1.74.2.1.2.9 libpopen2.tex,1.15.12.2,1.15.12.3

[fdrake@users.sourceforge.net]

Update of /cvsroot/python/python/dist/src/Doc/lib
In directory sc8-pr-cvs1:/tmp/cvs-serv8759/lib

Modified Files:
      Tag: release22-maint
	libos.tex libpopen2.tex 
Log Message:
Typo: "dead lock" --> "deadlock"

Index: libos.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/lib/libos.tex,v
retrieving revision 1.74.2.1.2.8
retrieving revision 1.74.2.1.2.9
diff -C2 -d -r1.74.2.1.2.8 -r1.74.2.1.2.9
*** libos.tex	12 Nov 2002 22:07:48 -0000	1.74.2.1.2.8
--- libos.tex	6 Dec 2002 16:43:48 -0000	1.74.2.1.2.9
***************
*** 332,336 ****
  module; these are only available on \UNIX.
  
! For a discussion of possible dead lock conditions related to the use
  of these functions, see ``\ulink{Flow Control
  Issues}{popen2-flow-control.html}''
--- 332,336 ----
  module; these are only available on \UNIX.
  
! For a discussion of possible deadlock conditions related to the use
  of these functions, see ``\ulink{Flow Control
  Issues}{popen2-flow-control.html}''

Index: libpopen2.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/lib/libpopen2.tex,v
retrieving revision 1.15.12.2
retrieving revision 1.15.12.3
diff -C2 -d -r1.15.12.2 -r1.15.12.3
*** libpopen2.tex	18 Jun 2002 20:38:43 -0000	1.15.12.2
--- libpopen2.tex	6 Dec 2002 16:43:58 -0000	1.15.12.3
***************
*** 130,134 ****
  When reading output from a child process that writes a lot of data to
  standard error while the parent is reading from the child's standard
! out, a dead lock can occur.  A similar situation can occur with other
  combinations of reads and writes.  The essential factors are that more
  than \constant{_PC_PIPE_BUF} bytes are being written by one process in
--- 130,134 ----
  When reading output from a child process that writes a lot of data to
  standard error while the parent is reading from the child's standard
! out, a deadlock can occur.  A similar situation can occur with other
  combinations of reads and writes.  The essential factors are that more
  than \constant{_PC_PIPE_BUF} bytes are being written by one process in