glance-cache-cleaner(1) [debian man page]
GLANCE-CACHE-CLEANER(1) Glance GLANCE-CACHE-CLEANER(1) NAME
glance-cache-cleaner - Glance Cache Cleaner GLANCE IMAGE CACHE INVALID CACHE ENTRY AND STALLED IMAGE CLEANER
Author glance@lists.launchpad.net Date 2012-01-03 Copyright OpenStack LLC Version 2012.1-dev Manual section 1 Manual group cloud computing SYNOPSIS glance-cache-cleaner [options] DESCRIPTION This is meant to be run as a periodic task from cron. If something goes wrong while we're caching an image (for example the fetch times out, or an exception is raised), we create an 'invalid' entry. These entires are left around for debugging purposes. However, after some period of time, we want to clean these up. Also, if an incomplete image hangs around past the image_cache_stall_time period, we automatically sweep it up. OPTIONS --version show program's version number and exit -h, --help show this help message and exit --config-file=PATH Path to a config file to use. Multiple config files can be specified, with values in later files taking precedence. The default files used are: [] -d, --debug Print debugging output --nodebug Do not print debugging output -v, --verbose Print more verbose output --noverbose Do not print verbose output --log-config=PATH If this option is specified, the logging configuration file specified is used and overrides any other logging options specified. Please see the Python logging module documentation for details on logging configuration files. --log-format=FORMAT A logging.Formatter log message format string which may use any of the available logging.LogRecord attributes. Default: none --log-date-format=DATE_FORMAT Format string for %(asctime)s in log records. Default: none --log-file=PATH (Optional) Name of log file to output to. If not set, logging will go to stdout. --log-dir=LOG_DIR (Optional) The directory to keep log files in (will be prepended to --logfile) --use-syslog Use syslog for logging. --nouse-syslog Do not use syslog for logging. --syslog-log-facility=SYSLOG_LOG_FACILITY syslog facility to receive log lines SEE ALSO o OpenStack Glance BUGS o Glance is sourced in Launchpad so you can view current bugs at OpenStack Glance AUTHOR
OpenStack COPYRIGHT
2010-present, OpenStack, LLC. 2012.1.1 March 14, 2013 GLANCE-CACHE-CLEANER(1)
Check Out this Related Man Page
syslog.conf(4) Kernel Interfaces Manual syslog.conf(4) NAME
syslog.conf - syslogd configuration file SYNOPSIS
facility.severity destination Where: Is part of the system generating the message, specified in /usr/include/sys/syslog_pri.h. See also the syslogd(8) reference page. The severity level, which can be emerg, alert, crit, err, warning, notice, info, or debug. See /usr/include/sys/syslog_pri.h. The syslogd daemon logs all messages of the specified severity level plus all messages of greater severity. For example, if you specify level err, all messages of levels err, crit, alert, and emerg or panic are logged. A local file pathname to a log file, a host name for remote logging or a list of users. In the latter case the users will receive messages when they are logged in. An asterisk (*) causes a message to be sent to all users who are currently logged in. DESCRIPTION
The /etc/syslog.conf file is a system file that enables you to configure or filter events that are to be logged by syslogd. You can specify more than one facility and its severity level by separating them with semicolons. You can specify more than one facility logs to the same file by separating the facilities with commas, as shown in the EXAMPLES section. The syslogd daemon ignores blank lines and lines that begin with an octothorpe (#). You can specify # as the first character in a line to include comments in the file or to disable an entry. The facility and severity level are separated from the destination by one or more tab characters. If you want the syslogd daemon to use a configuration file other than the default, you must specify the file name with the following com- mand: # syslogd -f config_file Daily Log Files You can specify in the /etc/syslog.conf file that the syslogd daemon create daily log files. To create daily log files, use the following syntax to specify the path name of the message destination: /var/adm/syslog.dated/ { file} The file variable specifies the name of the log file, for example, mail.log or kern.log. If you specify a /var/adm/syslog.dated/file path name destination, each day the syslogd daemon creates a sub-directory under the /var/adm/syslog.dated directory and a log file in the sub-directory, using the following syntax: /var/adm/syslog.dated/ date / file Where: The date variable specifies the day, month, and time that the log file was created. The file variable specifies the name of the log file you previously specified in the /etc/syslog.conf file. The syslogd daemon automatically cre- ates a new date directory every 24 hours and also when you boot the system. The current directory is a link to the latest date directory. To get the latest logs, you only need to reference the /var/adm/syslog.dated/current directory. EXAMPLES
The following is a sample /etc/syslog.conf file: # # syslogd config file # # facilities: kern user mail daemon auth syslog lpr binary # priorities: emerg alert crit err warning notice info debug # kern.debug /var/adm/syslog.dated/kern.log user.debug /var/adm/sys- log.dated/user.log daemon.debug /var/adm/syslog.dated/daemon.log auth.crit;syslog.debug /var/adm/syslog.dated/syslog.log mail,lpr.debug /var/adm/syslog.dated/misc.log msgbuf.err /var/adm/crash.dated/msgbuf.savecore kern.debug /var/adm/messages kern.debug /dev/console *.emerg * FILES
/etc/syslog.conf /etc/syslog.auth - Authorization file for remote logging. /usr/include/sys/syslog_pri.h - Common components of a syslog event log record. RELATED INFORMATION
Commands: /usr/sbin/syslogd(8), /usr/sbin/binlogd(8) System Administration delim off syslog.conf(4)