okpfud(1M)

SYNTAX

DESCRIPTION

The configuration file /etc/okpfid.d/okpfud.conf specifies specifies an <action> to be taken when a change is detected. When the <action> completes, okpfud examines the new state of the system, updates the information about the file in its internal tables, and resumes periodic scanning for changes in that file. You can request that okpfud re-read its configuration file by sending it a SIGHUP signal.

okpfud writes its process id number into the data file specified as <pid_file> on the command line. By default, this is /etc/okpfud.d/okpfud.pid.

Multiple fud processes can be run on one machine with each using a different configuration file and unique PID logging file.

Command line options

-f <configuration-file>

Use <configuration-file> rather than the default. See fud.conf(4) for the file syntax. <configuration-file> must be an absolute pathname.

-s <period>

Specify the interval, in seconds, between sweeps of the files that okpfud monitors. The default value is one second.

-p <pid_file>

Specify the location of the data file where PIDs are logged. If pid_file is an absolute file name (begins with /), the file can be located anywhere in the filesystem hierarchy. If pid_file does not begin with /, it will be located in the /etc/okpfud.d directory.

-v

Print version of okpfud command being executed.

-c

Execute the <action> for all monitored files once on system startup, before beginnng the regular scan for file changes. This option is useful when the system is in an unknown state on startup. It ensures that all files monitored by okpfud are up-to-date when fud starts.

-d, -D

Run okpfud in debug mode. -D specifies a more verbose mode than -d. Without these options, okpfud runs silently, logging warnings and error messages to the system log as discussed in syslog(3G). In debug mode, okpfud runs in the foreground rather than as a daemon and logs messages to stderr. These options are intended for debugging and should not be used on production systems.

SEE ALSO