• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..03-May-2022-

init.d/H02-Jun-2006-4028

CHANGESH A D02-Jun-200623.4 KiB561443

COPYRIGHTH A D02-Jun-20061.8 KiB4834

INSTALLH A D02-Jun-20069.8 KiB257203

MakefileH A D03-May-202218.8 KiB658168

READMEH A D02-Jun-20066.2 KiB121103

README.aixH A D02-Jun-2006878 1916

TODOH A D02-Jun-200610.3 KiB221182

doinkd.cH A D03-May-202244.4 KiB1,481973

doinkd.cf.man.formH A D02-Jun-200613.7 KiB574538

doinkd.cf.templateH A D02-Jun-20063.9 KiB12498

doinkd.hH A D03-May-20227.4 KiB233133

doinkd.man.formH A D02-Jun-20062.7 KiB8786

insque.cH A D02-Jun-2006462 3221

linetimelist.cH A D02-Jun-20062.8 KiB10867

list.cH A D02-Jun-20065.4 KiB196130

parse.yH A D02-Jun-20068.7 KiB398336

scan.lH A D02-Jun-20061.4 KiB7154

utmplines.cH A D02-Jun-20061,016 5731

version.hH A D02-Jun-200672 41

warn.cH A D03-May-202211 KiB400269

xlock_check.cH A D03-May-20226.1 KiB255206

zap.cH A D02-Jun-20069 KiB337225

README

1                             doinkd - Idle Deamon
2					     Author: Lott Caskey
3					       Copyright 2006
4
5			         Original Author: Michael Crider
6				    Copyright 1996 under name Idled
7
8
9INTRODUCTION
10        doinkd is a "daemon" that runs on a machine to keep an eye on current
11users.  If users have been idle for too long, or have been logged on for
12too long, it will warn them and log them out appropriately.  The types of
13checks that doinkd performs are the following:
14
15        maxuser:  *NEW* If a declared number of sessions, either by group or
16                  userid, are active, that user and subsequent users/sessions
17			   are warned and their sessions are terminated.
18
19        idle:     If a user is idle more than their allotted time, as
20                  specified by the doinkd configuration file, he/she will be
21                  warned.  If no action has taken place during the warn
22                  time, the user will then be logged out.
23
24        session:  If a user is logged on for longer than the allotted
25                  time, he/she will be warned and logged out in
26                  'warntime' seconds if the user is still logged on
27                  then.
28
29        multiple: If too many user sessions are active (ie. many users
30                  logged on, or some users logged on many times), doinkd
31                  will choose X many sessions for each user to keep,
32                  warning the others, and logging those out in 'sleep'
33                  seconds (such as 120) if there are still too many
34                  logged in then.  X is either specified as a number
35                  of multiples per user, or is proportional to the
36                  threshold of sessions before multiple logouts are
37                  in effect.
38
39        refuse:   If a user matches this setting, doinkd will terminate
40                  the user's session after about a 5 second warning.
41                  The basically "refuse"s access for that user (or
42                  tty, or group) to the machine, though there may be
43                  some time allowed when doinkd is sleeping between
44                  checks.
45
46FEATURES
47        doinkd is configurable without recompilation for its settings, such
48as the maximum allowed idle times, session limits, thresholds before
49session limits and multiple login checks begin, and also the important
50exemption lists.  The configuration file is automatically re-read every
51'sleep' seconds (specified in the configuration file).  If the
52configuration file missing or contains errors when doinkd attempts to update
53its configuration, it will simply report the errors to its log file and
54continue normal operation, either with its previous settings (in the event
55of the file not being there or not being readable) or with all valid
56settings (in the event of errors in the conf file).  doinkd must exit,
57however, if the configuration file is doesn't exist or is not readable when
58it first starts, and will also exit at the start if there are errors in the
59configuration file (since they should be fixed then).
60
61        Exemptions can be set for any user, group, host the user is logged
62in from, or tty for any of the checks that doinkd performs, such as allowing
63idle timeouts to default to 60 minutes for everyone, but exempting the
64'staff' group from these timeouts.
65
66        doinkd has the ability to handle the console as special, so that
67X-Windows environments can have appropriate settings.  The special handling
68includes giving an idle time, session limit, and allowed multiple logins
69specifically for the user on console.  All of these logout checks can also
70be disabled for the windows owned by the user on console.  Idle activity is
71found by checking the keyboard and mouse if the user is in X-Windows.
72Special checking is also done to see if the person on console is running
73xlock (or some terminal locking program--the name is configurable at
74compilation time) and logging the user off if the xlock program runs longer
75than the allowed console idle time.  The special xlock check prevents users
76from running xlock and leaving the terminal for a long period of time, but
77not getting logged off, since other users may press a key or move the mouse
78to see if the machine is available, and in doing so makes the logged in
79user no longer idle.  See TODO file for a comment on xlock.  doinkd also has
80the ability to work with some implementations of XDM.
81
82        The configuration file's path may be specified on the command line,
83so that one executable can be used on multiple machines with different path
84structures.  Also, doinkd can read in separate files (specified in the config
85file) to get a list of users to apply a timeout/session/refuse/exempt command
86to.
87
88SYSTEMS
89        Idled was written and tested extensively on Solaris 2.x.  Patches
90and good fortune have expanded it to HP-UX, SGI, Linux, AIX, BSDI, BSD/OS2,
91BSD (specifically SunOS 4.x), Ultrix, and DIGITAL Unix.  It may also work on
92other OS's.
93	Future developement of doinkd will be geared primarily toward BSD, Linux,
94SCO OpenServer and SCO Unixware systems with limited support for other similar
95style OS's.
96
97  Note: The xlock checking is not functional on some systems.
98        On BSDI and BSD/OS2, the console user will be killed
99        instanting if an xlock is running at all (if checking is
100        enabled in Makefile).  SunOS 4.x may not log off users on
101        console and not in openwin.
102
103ACKNOWLEDGEMENTS
104	doinkd is largely based on the code developed by Michael P. Crider called
105Idled.  The software has been such a great implimentation of monitoring user
106idle times that we decided to further extend its functionality while trying to
107keep the original authors views and developement plan in mind.
108	Idled originally was heavily based on the code from Untamo 3.
109We give many thanks to Craig Bishop of Deakin University for his rework of
110the original Untamo, as well as many thanks to Andy Wilcox and Marc Megel
111of Purdue University for their hard work on the original Untamo.  Idled
112certainly would not have all the functionality it has if it was not for
113these people.
114
115AVAILABILITY
116	doinkd can be downloaded from 'http://sourceforge.net/projects/idled'.
117
118	idled was last available from the orignal author at
119	'http://www.darkwing.com/idled'.  And is also being supplied at the
120	Source Forge page for reference purposes.
121

README.aix

1This is an exert from the Idled documentation which should also apply
2to doinkd.
3---------------------
4The changes required to make idled work under AIX were relatively minor.
5For the most part they were a matter of changing which include files were
6used and fixing a problem with the definition of NGROUPS, which is a macro
7under AIX (idled expected it to be a simple number).  The exception to this
8is xlock checking.  The present set of patches disable xlock checking due
9to problems with the method used to determine if xlock is running and for
10how long.  Hopefully I can have this corrected in the next set of patches
11for AIX.  Other than this, idled compiles and runs ok, but has not yet been
12tested very much.
13
14Tom Schenk
15tschenk@risc.austin.ibm.com
16
17IBM in no way endorses these patches.  The patches applied simply allow
18idled to compile for me.  Use at your own risk.
19