Specifications

Loadable Modules
13-13
The -l option instructs modadmin to load a loadable module into the running system.
For example, the command
modadmin -l lp
loads a line printer driver named lp.
If the lp driver references symbols in other loadable modules (as defined in the $depend
line in its Master file), and some or all of these modules are not already loaded,
modadmin loads them along with the lp driver. When loading completes, modadmin
prints (on stdout) an integer module-id used to identify driver lp.
Querying the Module's Status 13
Once you have loaded your driver, you can view status information about the driver using
the -Q, -q, -S, or -s options. For example, the command
modadmin -Q lp
requests status for the lp driver by specifying its module name, and the command
modadmin -q module-id
requests status for the lp driver by specifying the module-id returned by the -l option.
Information returned by the -Q and -q options includes the driver's auto-unload delay
value, its hold count (the number of holding put on the driver), its dependent count (the
number of loadable module depends on the driver), and the pathname to its object file on
disk.
The -S and -s options are used alone with modadmin, and request full and abbreviated
status for all modules currently loaded, respectively.
Modifying the DLM Search Path 13
If you have placed your driver's loadable image somewhere other than in the default direc-
tory /etc/conf/mod.d, you need to give DLM the pathname to this location using the
modadmin command with the -d option before you attempt to load your driver.
For example, if you had installed the lp driver on a remote server in a directory named
/nfs/mod.d, you would use the command
modadmin -d /nfs/mod.d
to prepend the directory /nfs/mod.d to the search path DLM uses to locate loadable
modules on disk.
Or, you can specify the full pathname to the loadable module when loading with the -l
option. For example,
modadmin -l /ufs/mod.d/lp