kclog(1M)kclog(1M)NAMEkclog - manage kernel configuration log file
config] string] type] name] [count]
is the administrative command for the HP-UX kernel configuration log
file. The log file is automatically maintained by all of the kernel
configuration commands (and Any change to any kernel configuration gets
logged to this log file, which is located at Note that this file is a
plain text file which can be viewed and manipulated using standard Unix
file management commands; exists simply for convenience in finding par‐
ticular log file entries.
Under normal usage, prints the last count entries in the log file.
When one of the options is specified, prints the last count entries
that match the specified criteria. If count is not specified, it
defaults to 1.
will print all entries matching criteria. If this option is not speci‐
will only print the last count entries that match the
will print only log file entries describing changes to the saved
kernel configuration named config. If this option is
not specified, will print log file entries describing
changes to any saved or running kernel configuration.
will not print any entries. Instead,
will create a new entry, as if a kernel configuration
change had been made, containing the specified comment.
This option is only allowed for users with appropriate
will print only log file entries that contain the given
will print only log file entries that refer to a configuration object
(module or tunable) of the given name.
will print only log file entries that refer to configuration objects
of the specified type: or
returns zero for success. It returns non-zero and prints a diagnostic
message if an error occurs.
To see the last three entries in the log:
To see the last entry for the tunable
To see the last five entries for module changes:
To see all entries for module changes:
To see the last entry mentioning Aberdeen:
The format of the log file may be changed without notice.
Some configuration changes can be made without using the kernel config‐
uration commands. No log file entries are made for such changes.
The log file should not be manually edited. Doing so may cause to
SEE ALSOkcmodule(1M), kconfig(1M), kctune(1M), kconfig(5).