load(7) [suse man page]

LOAD(7) 							   SQL Commands 							   LOAD(7)

NAME

       LOAD - load a shared library file

SYNOPSIS

       LOAD 'filename'

DESCRIPTION

       This  command loads a shared library file into the PostgreSQL server's address space. If the file has been loaded already, the command does
       nothing. Shared library files that contain C functions are automatically loaded whenever one of their functions is called.   Therefore,	an
       explicit LOAD is usually only needed to load a library that modifies the server's behavior through ``hooks'' rather than providing a set of
       functions.

       The file name is specified in the same way as for shared library names in CREATE FUNCTION [create_function(7)]; in particular, one can rely
       on  a  search  path  and  automatic addition of the system's standard shared library file name extension. See in the documentation for more
       information on this topic.

       Non-superusers can only apply LOAD to library files located in $libdir/plugins/ -- the specified filename  must	begin  with  exactly  that
       string. (It is the database administrator's responsibility to ensure that only ``safe'' libraries are installed there.)

COMPATIBILITY

       LOAD is a PostgreSQL extension.

SEE ALSO

       CREATE FUNCTION [create_function(7)]

SQL - Language Statements					    2010-05-14								   LOAD(7)

MODULES-LOAD.D(5)						  modules-load.d						 MODULES-LOAD.D(5)

NAME

       modules-load.d - Configure kernel modules to load at boot

SYNOPSIS

       /etc/modules-load.d/*.conf

       /run/modules-load.d/*.conf

       /usr/lib/modules-load.d/*.conf

DESCRIPTION

       systemd-modules-load.service(8) reads files from the above directories which contain kernel modules to load during boot in a static list.
       Each configuration file is named in the style of /etc/modules-load.d/program.conf. Note that it is usually a better idea to rely on the
       automatic module loading by PCI IDs, USB IDs, DMI IDs or similar triggers encoded in the kernel modules themselves instead of static
       configuration like this. In fact, most modern kernel modules are prepared for automatic loading already.

CONFIGURATION FORMAT

       The configuration files should simply contain a list of kernel module names to load, separated by newlines. Empty lines and lines whose
       first non-whitespace character is # or ; are ignored.

       Each configuration file shall be named in the style of program.conf. Files in /etc/ override files with the same name in /usr/lib/ and
       /run/. Files in /run/ override files with the same name in /usr/lib/. Packages should install their configuration files in /usr/lib/, files
       in /etc/ are reserved for the local administrator, who may use this logic to override the configuration files installed from vendor
       packages.

       If the administrator wants to disable a configuration file supplied by the vendor, the recommended way is to place a symlink to /dev/null
       in /etc/modules-load.d/ bearing the same filename.

EXAMPLE

       Example 1. /etc/modules-load.d/virtio-net.conf example:

	   # Load virtio-net.ko at boot
	   virtio-net

SEE ALSO

       systemd(1), systemd-modules-load.service(8), systemd-delta(1), modprobe(8)

systemd 208															 MODULES-LOAD.D(5)