This file describes known bugs.

This program was written from scratch.  I've yanked a few
subroutines and proceedures from some man pages, but
that is about it.  If there are any bugs, they are mine.

The log file setting in the config file overrides the
command line setting.

There will be "memory leaks" since there is not (yet)
a facility for removing stale cached answers.  This
feature is forthcoming.  Also, a cached answer is created
for each and every unnamed uid that owns a socket and
is queried.  If your system has lots of users, this
may be unmanagable.

The "error: actual" setting is neither documented nor
implemented correctly, as it can be set in a
user's file.

If a user's file cannot be read, the program continually
assumes that the cached data is out of date, and rebuilds
it.  I think the worst that can happen is a small
performance hit.

The responses are NOT truncated to 512 octets as documented.

The security specifics may not behave sensibly for the
"setuid-non-root and invoked by root" case.

The pid file cannot be removed unless the runas_uid
owns the parent directory.  This requires a little extra
setup from the administrator.  Suggested workaround is
to create a script runnable only by root that removes
the pidfile, or set the default pidfile in a directory
owned by the runas_uid.

If the pidfile exists the program aborts.

Directories that are used by the pidfile, logfile, and
the user data files are not created if they don't exist.


There is no man or info page :-/