On Fri, 14 Mar 2008 21:50:17 -0400 =?utf-8?b?RnLDqWTDqXJpYyBCcmnDqHJl?= <
> 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. This is easy to solve by changing LOCKDIR to point to something you can access. You presumably are setting a custom configuration file to run as non-root (since you wont be able to read /etc/logcheck/logcheck.conf without sudo), and then that custom config file can change the location to /tmp or wherever. I think this already works in the version in bookworm, so perhaps we can close this bug
