The accompanying two files are a binary (executable) for a unix script
program for the 3B1. unfortunately, i have lost the source (defective
floppy storage). i compiled it under os3.51 fr omy 3B1s, and kept it
in /usr/local/bin/script. i do not know if it is specific to that
location - don't see why it should be. that is the file script. the
file script.1 is the man entry for srcipt. i maintained man and catman
for my add-ons to the 3B1's os.  it would be nice to verify that it
runs on someone else's machine. please let me know about any problems.
			awouk@nilenet.com



the following is the output of man on script.1:



     SCRIPT(1l)                                             SCRIPT(1l)



     NAME
          script - record a terminal session

     SYNOPSIS
          script [ -aq ] [ -s _s_h_e_l_l ] [ _f_i_l_e ]

     DESCRIPTION
          _S_c_r_i_p_t records an interactive session in a file as it
          appears on the tty.

          If _f_i_l_e is specified, the script is recorded in _f_i_l_e.
          Otherwise, the session is recorded in typescript in the
          current directory. The -s option causes _s_h_e_l_l to be used
          instead of that specified by the SHELL environment variable.
          If SHELL is not defined, the default is /bin/sh. Other
          options and their actions are:

          -a  Append to the script file.  Otherwise, the file is
              truncated.

          -q  Quiet mode.  Don't print the time and date at the
              beginning and end of the script.

     FILES
          ./typescript

     SEE ALSO
          sh(1), csh(1), ksh(1) or whatever you use.

     DIAGNOSTICS
          Various complaints when _o_p_e_n(2), _f_o_r_k(2), _e_x_e_c(2), or
          _p_i_p_e(2) calls fail.

     BUGS
          User input and program output are intercepted by different
          processes; they might not appear in the same order in the
          script file as they did on the tty.

          This is a generic version, using only pipes.  It should work
          on any reasonable imitation of Unix, but knows nothing about
          sockets, Streams or ptys.  Programs which care whether they
          are talking to a tty might not work right.  Commands like
          _p_s(1) which care about process groups probably won't work
          right.











     Page 1                                          (printed 4/30/93)