User's Guide for MS-DOS Clients

256
Basic Reference
Using UNIX System Commands
Most programs produce some kind of output or data. When you use netrun,
this output is sent to your screen. To send the output to a file, specify a >path
to receive the output in the netrun command line. By default, LAN Manager
creates this file in the current directory. If you specify a drive letter, netrun
assumes the drive is one of the workstation’s drives.
Because the Netrun service runs as a daemon process on the UNIX system
server without a controlling terminal, and because any command executed
by netrun inherits this state, those programs that issue input prompts when
they detect that they are being run from the command line will not issue
prompts.
Commands that can be run with the netrun command are controlled by the
Netrun service on the computer that has the executable file. For example, the
shell detects whether there is a controlling terminal and issues the PS1
prompt while waiting for command input. It does not do this when input is
not coming from a terminal (for example, when it is running a shell script
from a file). When run from netrun, the shell will not issue any prompts. A
sample session follows:
D:> netrun sh
date
Wed Sep 2 17:20:26 PDT 1992
who
root console Aug 24 12:31
exit
D:>
When using the netrun program on an MS-DOS client, the keyboard input
is buffered, and lines are sent only when the buffer fills or a return is entered.
This may require entering a return after some special characters to get them
sent across. For example, when entering expressions to the UNIX system bc
program, you might type the following:
D:> netrun bc
3+4
7
If you then intend to exit bc by typing CTRL+D (which would normally
terminate bc immediately), you need to follow the CTRL+D with a carriage
return to send the CTRL+D to the server.