Package: libpam-shield Version: 0.9.2-3.1 Followup-For: Bug #488841 Ah, looking at the source, I figured out part of it. Since the cron purge job only runs once a day, it doesn't do anything to have the retention period set to less than a day. I added a file in cron.d to run every three minutes instead.
The "Can't be writer" part is still an issue, though based on the (new) information that the cronjob only runs once per day, the "writer" errors are all caused by network accessess. I am using libpam-shield for POP and FTP accesses, which can have a couple accesses per second, though not sustained - ie. two requests might come in at the same second, but if one was delayed a second to get the lock or whatever is needed to write to the database, that would work on my site. I don't know if there is a solution for larger sites. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (SMP w/2 CPU cores) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) Shell: /bin/sh linked to /bin/bash Versions of packages libpam-shield depends on: ii libc6 2.7-10 GNU C Library: Shared libraries ii libgdbm3 1.8.3-3 GNU dbm database routines (runtime ii libpam0g 0.99.7.1-6 Pluggable Authentication Modules l libpam-shield recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
