Logcheck devel - Mar 2008 - Bug#470997: logcheck: allow running w/o locking

Package: logcheck
Version: 1.2.63
Severity: wishlist

When testing a checked-out copy of the rulefiles against an old log copy
and sending the output to stdout, I still have to use sudo because
logcheck insists on creating a lockfile.  It'd be nice to provide an
option to skip that part.


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (1001, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.18 (SMP w/1 CPU core)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages logcheck depends on:
ii  adduser            3.106                 add and remove users and groups
ii  bsd-mailx [mailx]  8.1.2-0.20071201cvs-2 A simple mail user agent
ii  cron               3.0pl1-103            management of regular background p
ii  lockfile-progs     0.1.11-0.1            Programs for locking and unlocking
ii  logtail            1.2.63                Print log file lines that have not
ii  mailx              1:20071201-2          Transitional package for mailx ren
ii  postfix [mail-tran 2.5.1-1               High-performance mail transport ag
ii  sysklogd [system-l 1.5-2                 System Logging Daemon

Versions of packages logcheck recommends:
ii  logcheck-database             1.2.63     database of system log rules for t

-- no debconf information