*** UNIX MANUAL PAGE BROWSER ***

A Nergahak database for man pages research.

Navigation

Directory Browser

1Browse 4.4BSD4.4BSD
1Browse Digital UNIXDigital UNIX 4.0e
1Browse FreeBSDFreeBSD 14.3
1Browse MINIXMINIX 3.4.0rc6-d5e4fc0
1Browse NetBSDNetBSD 10.1
1Browse OpenBSDOpenBSD 7.7
1Browse UNIX v7Version 7 UNIX
1Browse UNIX v10Version 10 UNIX

Manual Page Search

Manual Page Result

0 Command: pkopen | Section: 3 | Source: UNIX v7 | File: pkopen.3
PKOPEN(3) Library Functions Manual PKOPEN(3) NAME pkopen, pkclose, pkread, pkwrite, pkfail - packet driver simulator SYNOPSIS char *pkopen(fd) pkclose(ptr) char *ptr; pkread(ptr, buffer, count) char *ptr, *buffer; pkwrite(ptr, buffer, count) char *ptr, *buffer; pkfail() DESCRIPTION These routines are a user-level implementation of the full-duplex end- to-end communication protocol described in pk(4). If fd is a file de- scriptor open for reading and writing, pkopen carries out the initial synchronization and returns an identifying pointer. The pointer is used as the first parameter to pkread, pkwrite, and pkclose. Pkread, pkwrite and pkclose behave analogously to read, write and close(2). However, a write of zero bytes is meaningful and will pro- duce a corresponding read of zero bytes. SEE ALSO pk(4), pkon(2) DIAGNOSTICS Pkfail is called upon persistent breakdown of communication. Pkfail must be supplied by the user. Pkopen returns a null (0) pointer if packet protocol can not be estab- lished. Pkread returns -1 on end of file, 0 in correspondence with a 0-length write. BUGS This simulation of pk(4) leaves something to be desired in needing spe- cial read and write routines, and in not being inheritable across calls of exec(2). Its prime use is on systems that lack pk. These functions use alarm(2); simultaneous use of alarm for other pu- poses may cause trouble. deprecated PKOPEN(3)

Navigation Options