Man page or keyword search:   man All Sections 1 - General Commands 2 - System Calls 3 - Subroutines, Functions 4 - Special Files 5 - File Formats 6 - Games and Screensavers 7 - Macros and Conventions 8 - Maintenence Commands 9 - Kernel Interface New Commands Server 4.4BSD AIX Alpinelinux Archlinux Aros BSDOS BSDi Bifrost CentOS Cygwin Darwin Debian DigitalUNIX DragonFly ElementaryOS Fedora FreeBSD Gentoo GhostBSD HP-UX Haiku Hurd IRIX Inferno JazzOS Kali Knoppix LinuxMint MacOSX Mageia Mandriva Manjaro Minix MirBSD NeXTSTEP NetBSD OPENSTEP OSF1 OpenBSD OpenDarwin OpenIndiana OpenMandriva OpenServer OpenSuSE OpenVMS Oracle PC-BSD Peanut Pidora Plan9 QNX Raspbian RedHat Scientific Slackware SmartOS Solaris SuSE SunOS Syllable Tru64 UNIXv7 Ubuntu Ultrix UnixWare Xenix YellowDog aLinux   6284 pages apropos Keyword Search (all sections) Output format html ascii pdf view pdf save postscript

MODLOG(8)		  BSD System Manager's Manual		     MODLOG(8)

NAME
     modlog - display mod status

SYNOPSIS
     modlog [-p root] [logfile]

DESCRIPTION
     The modlog command displays the current status of mods on the system.
     Both user and kernel mods are displayed (from their default log files).
     The mod status for a particular kernel tree can be displayed by running
     modlog from the top of that kernel tree.

     If logfile is specified then mod status will only be reported from the
     file given.

     If a root directory is specified (via -p or the environment variable
     ROOT) then the default log file locations used will be relative to that
     root.

   OPTIONS

     -p root
	  Use root as the root of the directory tree for the purposes of lo-
	  cating the mod log files.

ENVIRONMENT
     ROOT	 Use ROOT as the root of the directory tree for the purposes
		 of locating the mod log files. The -p flag overrides ROOT.

FILES
     The following log files are searched for by default:
     /var/db/install.log	  User mod log file.
     /usr/src/sys/PATCHLOG	  Kernel mod log file.
     ./PATCHLOG			  Kernel mod log file in current directory.

EXAMPLE
     # modlog

     Kernel mods   [/usr/src/sys/PATCHLOG]

     Mod name	     Status	   Date
     ----------	     ---------	   --------------------
     SK300-001	     Applied	   Thu Apr 17 10:33:28 MDT 1997
     BK300-001	     Applied	   Thu Apr 17 10:33:29 MDT 1997

SEE ALSO
     patch(1)

BUGS
     When displaying the PATCHLOG mod log in the current directory, the con-
     tents of /usr/src/sys/PATCHLOG will still be displayed - this may result
     in duplicated output.

BSDI BSD/OS			April 16, 1997				     1

Vote for polarhome