Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

memlockd(8) [debian man page]

memlockd(8)						      System Manager's Manual						       memlockd(8)

NAME
memlockd - daemon to lock files in memory with mlock SYNOPSIS
memlockd [ -c config-file ] [ -d ] [ -f ] [ -u user ] DESCRIPTION
This manual page documents briefly the memlockd command. It is used to lock system programs and config files in memory so that if a DOS attack is experienced then the chance of the sys-admin regaining control of the system in a reasonable amount of time (and therefore having a reasonable chance of discovering the cause of the problem) is significantly increased. OPTIONS
The -c option is used to specify the fully-qualified path name to a config file that lists the names of files to lock, if the config file is not specified then it will default to /etc/memlockd.cfg. In any situation where a config file is used a directory can be used instead, for a directory every file ending in ".cfg" will be processed. The -d option specifies debugging mode, the program will not fork and will produce it's logging messages on stderr instead of via syslog. The -f option specifies foreground (non-daemon) mode, the program will not fork but will still log normally. The -u option specifies the name of a user to use for running ldd (for recursive operation). Note that locking shared objects that are writable by non-root is not safe, but using a different UID will reduce the risk. The config file will contain a number of fully qualified names of files to lock in RAM. When locking shared objects and ELF binaries it is possible to prefix the file name with a + character to indicate that memlockd should recursively lock all shared objects that the program requires and all shared objects that those objects require. When a file not found error doesn't matter (EG you want a single config file to have the file names for multiple architectures or systems) you can prefix the file name with a ? character, in that case errors such as EPERM will still be logged. If a line in the config file starts with a % character it will be taken as the name of a config file or directory to process. Currently only one level of recursion is accepted. SEE ALSO mlock(2), mmap(1). AUTHOR
memlockd was written by Russell Coker <russell@coker.com.au> memlockd(8)

Check Out this Related Man Page

clfdomainsplit(1)							 1							 clfdomainsplit(1)

NAME
clfdomainsplit - split Common-Log Format web logs based on domain name SYNOPSIS
clfdomainsplit [--help] [-i input] [-d defaultfile] [-c cfg-file] [-o directory] DESCRIPTION
The clfdomainsplit program will split up large CLF format web logs based on domain name. This is for creating separate log analysis passes for each domain hosted on your server. OVERVIEW
The input parameter specifies the file to read (default is standard input). The defaultfile parameter specifies where data goes if it doesn't have a domain (either it has an IP address for the server or it doesn't have the server-name - the URL is relative to the root of the web server only). The default will be to print them on standard error. The cfg-file parameter is for specifying the rules for determining what is a different domain name. For example www.coker.com.au belongs in the same file as coker.com.au and abc.coker.com.au because domain names ending in .au have three major components. The domain names www.workbenelux.nl and workbenelux.nl belong in the same file because domain names ending in .nl have two major components (as do .com, and .gov), wheras anything ending in .va belongs to the same organization. The rules are of the form number:pattern which lists the number of domain parts which are significant (2 for .com and for a simple string comparison, the default will be: 2:com 2:nl 3:au 3:uk If no config file is specified then it will look for /etc/clfdomainsplit.cfg. Of course comments start with #. Also note that the first match will be used! The directory parameter is to specify the location for the files to be created (default is the current directory). I recommend that you use a directory for this and nothing else as you never know how many files may be created! EXIT STATUS
0 No errors 1 Bad parameters AUTHOR
This program, its manual page, and the Debian package were written by Russell Coker <russell@coker.com.au>. SEE ALSO
clfsplit(1),clfmerge(1) russell@coker.com.au 0.06 clfdomainsplit(1)
Man Page