Lines Matching full:figure

206 Figure 1\ \ Use of a pipe
221 its child and itself (Figure 1).
226 In Figure 1, the parent process makes a call to the system routine 
240 Figure 2 illustrates the effect of a fork.
248 Figure 2\ \ Sharing a pipe between parent and child
281 The program in Figure 3 calls \fIsocketpair()\fP
285 Figure 4 illustrates the result of a fork following a call to 
318 Figure 3\ \ Use of a socketpair
323 Figure 4\ \ Sharing a socketpair between parent and child
414 it is created.  For example, in Figure 5a the call to \fIsocket()\fP
425 Figure 5a\ \ Reading UNIX domain datagrams
439 The program in Figure 5a uses the name ``socket'',
442 The routines in Figure 5b use its
450 Figure 5b\ \ Sending a UNIX domain datagrams
471 parties.  In the example, the program in Figure 5b gets the
485 Figure 6a\ \ Reading Internet domain datagrams
488 The examples in Figure 6a and 6b are very close to the previous example
519 Figure 6b\ \ Sending an Internet domain datagram
526 The wildcard value is used in the program in Figure 6a.
533 The program in Figure 6b is given the destination host name as a command
603 Figure 7a\ \ Initiating an Internet domain stream connection
610 Figure 7b\ \ Accepting an Internet domain stream connection
616 Figure 7c\ \ Using select() to check for pending connections
622 Figure 8\ \ Establishing a stream connection
626 program in Figure 7a, requests a connection with a particular socket,
630 situation is illustrated in the top half of Figure 8.  Process 2
641 The program in Figure 7b is a rather trivial example of a server.  It 
656 connection is created.  The bottom half of Figure 8 shows the result of
669 The program in Figure 7c is a slight variation on the server in Figure 7b.
690 Figure 9a\ \ Initiating a UNIX domain stream connection
696 Figure 9b\ \ Accepting a UNIX domain stream connection
767 The various options for reading and writing are shown in Figure 10,
819 Figure 10\ \ Varieties of read and write commands