10.0;inlib (install_library), revision 1.0, 88/03/21
inlib (install_library) -- Install a user-supplied library.
usage: inlib pathname...
DESCRIPTION
inlib installs a library at the current shell level; it remains installed
until the shell that installed it exits. See the note below for
information on loading a library that is used by all processes. The
newly installed library will be used to resolve external references of
programs (and libraries) loaded after its installation. (Thus,
previously loaded libraries and programs will not be affected.)
Note that only those global references that are marked by the binder
become visible, and that the default action of the binder is to leave
globals unmarked. Therefore, you should take care to mark all
appropriate globals when you bind your library.
inlib is an internal shell command.
NOTE
For performance reasons, we recommend that you use bind -inlib in place
of inlib. inlib directs each subsequent invoked process to install the
library; using bind with the -inlib option, the library is installed only
with the required programs. See the bind command. You can create a
library that is installed automatically in every process. This library
resides in the file /lib/userlib.private. The procedure text in this
library will be shared among all processes.
This library must be present at node start-up time in order to be
installed. After copying your library to /lib/userlib.private, you must
shut down the node and start it up again in order to use the library.
Changes to the library also require rebooting the node to load the new
routines.
Global names in /lib/userlib.private must not duplicate names used in
Domain libraries.
pathname (required)
Specify name of library file(s) to be installed. Multiple
pathnames and wildcarding are permitted.