|Configuration file which specifies how often doinkd is to wake up, and exemptions to rules, etc. There is no need to restart doinkd to change the configuration. If changes are made to this file, doinkd will re-read the configuration rules.|
|Log of when doinkd is started, killed, who it logs off and why, and any errors it encounters.|
The newest version of doinkd is available from http://sourceforge.net/projects/idled
All comments and suggestions for doinkd would be greatly appreciated and should be sent to lottc at SpinnakerResorts dot com
Various couldnt open ... error messages. Since doinkd dissacociates itself from the invoking terminal, most of the errors get put in the log file.
If a user logs off and then on again fast enough and manages to get a different tty, he may be warned about a multiple login.
It will not warn the person on console about being logged off if that person is not in X-Windows, since things get really screwy then (due to some weirdness in the system blocking reading of the utmp file until a person hits <return> on the consoles keyboard-- and that is one <return> for each utmp line!).
If doinkd is started considerably after a users session limit is up, it will warn that it is waiting "warn" time before killing the session, but will actually only wait 10 seconds (which is adjustable via a line in chk_session() in doinkd.c). I left this because it would be somewhat messy to fix it, when it will probably not have much effect anyway.
|-->||DOINKD (8)||May 30, 2006|