Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

lurker-prune(1) [debian man page]

LURKER-PRUNE(1) 					      General Commands Manual						   LURKER-PRUNE(1)

NAME
lurker-prune -- prunes the web-server cache SYNOPSIS
lurker-prune [-c <config-file>] [-f <frontend>] [-m <days>] [-a <days>] [-p -v] DESCRIPTION
lurker-prune prunes obsolete or stale files from the web-server accessible cache. This command must be run at regular intervals from eg. a cronjob. If it is not run, then the lurker web interface will appear to not be receiving new mail or have contradictory links between pages. A good interval is every 15 minutes and should not exceed one hour. Be aware that it is possible for an attacker to use up a large amount of disk space through lurker. An attacker could request many distinct lurker web pages each of which is cached, thus using disk space. Please setup a quota for the lurker user, read your logs, and follow what- ever site-specific policies you have for denial of service. A good script to run in parallel with normal lurker-prune use is one similar to: if test `du -s /var/www/lurker | cut -f1` -gt 32768; then lurker-prune -p; fi This might help guard against a potential denial-of-service attack. OPTIONS
-c config-file Use this config file for lurker settings. -f frontend The directory of the lurker frontend cache to clean. You can selectively purge cache with this option. By default, lurker-prune will clean all frontends specified in the config file. -m days Keep cached files for at most this many days. Any cached file regardless of last access will be deleted after the specified num- ber of days (defaults to 7). Files which are obsolete due to new mail, config changes, or no accesses will be deleted earlier. Deleted files will be automagically regenerated if needed. -a days Kill cache files not accessed for this many days. Any cached file which has not been read from for the specified number of days (defaults to 1) will be deleted. Files which are obsolete due to new mail or config changes will be deleted earlier. Deleted files will be automagically regenerated if needed. -p Purge mode. Delete all cache files even if they do not appear to be expired. This will only deletes files that are generated by lurker, and is thus preferable to rm */*. -v Verbose operation. Indicate which files are being deleted and the reasoning behind lurker's decisions. This can help in tracking down why some files are deleted and not others. SEE ALSO
lurker-index(1), lurker-params(1), lurker-list(1) lurker documentation on http://lurker.sourceforge.net/ COPYRIGHT
Copyright (C) 2002: Wesley W. Terpstra <terpstra@users.sourceforge.net> This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MER- CHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. BUGS
Before reporting a bug, please confirm that the bug you found is still present in the latest official release. If the problem persists, then send mail with instructions describing how to reproduce the bug to <lurker-users@lists.sourceforge.net>. LURKER-PRUNE(1)

Check Out this Related Man Page

MAILMAN2LURKER(8)					      Administrative commands						 MAILMAN2LURKER(8)

NAME
mailman2lurker - Import mailman lists and their archives into a lurker database. SYNOPSIS
mailman2lurker -i|-p [options] DESCRIPTION
mailman2lurker has mainly two functions. First, it parses mailman's lists and creates a lurker configuration include out of them. Second, it imports archives from mailman lists into a lurker database. To build a new lurker database from mailmans archives, first run 'mailman2lurker -p'. Next you need to add 'include = /etc/lurker/lurker.conf.mailman' into /etc/lurker/lurker.conf.local. Finally import mailmans mboxes by running 'mailman2lurker -i'. If you want to add new lists to an already existing lurker configuration, run 'mailman2lurker -p -w newlists' and afterwards 'mailman2lurker -i -f newlists'. This will import only the mbox files of mailman lists that have been added to the lurker configuration because they were new to lurker. COMMANDS
-p, --parse Parse mailman lists, and create a lurker configuration include file containing all parsed lists. Lists that are already configured in lurker are ignored. -i, --import Import archives of all lists. This parses the lurker configuration and imports the mailman mbox at /var/lib/mailman/archives/private/<list>.mbox/<list>.mbox for every list. OPTIONS
-c, --config <config> Use <config> as lurker configuration file. Default: /etc/lurker/lurker.conf -o, --outfile <outfile> Write list configuration to <outfile>. If this is not specified, <lurker.conf>.mailman will be used. This option is only useful in conjunction with -p. -g, --group <group> Use <group> for new lists. Default is 'undef'. This option is only useful in conjunction with -p. -a, --listhost <listhost> Use <listhost> as host for new list addresses. If a new list is called 'mylist' and <listhost> is lists.org, then the list address will be mylist@lists.org. Default is 'example.org'. This option is only useful in conjunction with -p. -l, --link <url link> Use <url link> as base for links of new lists. If a list is called 'mylist', and <url link> is 'http://lists.org', then the link address will be http://lists.org/mylist. Default is 'http://example.org'. This option is only useful in conjunction with -p. -s, --lang <language> Use <language> as language for new lists. Needs to be a language token. Default is 'en'. This option is only useful in conjunction with -p. -w, --write-lists <file> Write a list of all lists that have been added to the lurker configuration. Safe that list in <file>. Default is off. This option is only useful in conjunction with -p. -x, --list-cmd <file> Use <command|file> to get the list of mailman lists that should be parsed. When <command|file> is a command, it needs to end with ' |'. Default is '/var/lib/mailman/bin/list_lists |'. This option is only useful in conjunction with -p. -f, --listfile <file> Import only lists that are listed in <file>. This option is only useful in conjunction with -i. -d, --lists <one[,two,...]> Import only lists that are given as argument. This option is only useful in conjunction with -i. -h, --help Display a help message. -v, --version Display mailman2lurker's version number. SEE ALSO
list_lists(8), lurker-index(8) AUTHOR
This program was written by Jonas Meurer <jonas@freesources.org>. COPYRIGHT
mailman2lurker may be copied and modified under the terms of the GNU General Public License. 2011-09-19 MAILMAN2LURKER(8)
Man Page

Featured Tech Videos