Hi Bill,
On 10/02/2013 01:06 AM, Bill Wohler wrote:
Package: libpam-abl
Version: 0.4.3-1
Severity: normal
Today I tried to whitelist one of my hosts with the following results.
The second pam_abl listing hung and had to be interrupted with C-c.
$ sudo pam_abl
<expected listing>
$ sudo pam_abl --whitelist -H <host>
No such file or directory (2) while reading config file
Invalid argument (22) while reading config file: No db_home dir specified
$ sudo pam_abl
pam-abl: unable to join the environment
pam-abl: unable to join the environment
^C $
I removed all of the files in my pam-abl database directory
(db_home=/var/lib/abl/) and this cleared up the problem.
In addition to having a corrupted database, the error message above is
incorrect; as you can see, db_home *is* specified.
Note that I just upgraded to wheezy, so I'm suspecting a database
upgrade had a role to play. If this is true, please retitle this issue
yes, it is very likely that the database upgrade caused the problem.
to "Upgrading database version corrupts database." Dependencies should
be put in place so that the pam-abl database is automatically rebuilt
upon a database upgrade. At the very least, documentation should be
added to /usr/share/doc/libpam-abl/README.Debian. For example, please
see Section 2.6, Updating Berkeley DB version underneath bogofilter, in
/usr/share/doc/bogofilter-bdb/README.db.
Regarding the upgrade procedure, I am not sure that it makes sense to
implementing a tool which will upgrade databases during install/update
Currently I mentioned in the README.Debian that one should delete the
old databases or try to upgrade them manually in case of libdb upgrade.
Btw, I've recently uploaded to experimental a new release - 0.6.0.
It has important changes, but unfortunately the binary package will not
work on wheezy because of dependencies.
If you are willing to test it I'll provide the guidelines on how to
build it for wheezy.
Sorry for such a long delay and best regards,
Alex
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
