1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
|
.TH IDLED 8 "October 22, 1995"
.SH NAME
idled \- Idle terminal and multiple login monitor daemon.
.SH SYNOPSIS
.B idled
[-f
.B config_file
]
.SH DESCRIPTION
.PP
.I Idled
wakes up at regular intervals and scans the system's
.B utmp
file to see
which users are currently logged in, how long they have been idle,
whether they are logged in more than once, etc.
.I Idled
then warns and logs out users based on a set of rules in its
configuration file.
.I Idled
is usually started from /etc/rc.local on SunOS 4.x (and perhaps other
BSD systems) or from a script something like S95idled in /etc/rc3.d
on Solaris 2.3 (and perhaps other SVR4 systems).
.PP
.I Idled
uses a configuration file,
.IR idled.cf ,
to find out how long a terminal must be unused to be considered
\*(lqidle\*(rq, and which users, groups, terminals, or clusters of
terminals are exempt from being logged out.
.PP
The path of the configuration file, which is compiled in, can be overriden
by using the flag
.B -f
followed by the name of the configuration file to use (and path,
if necessary).
.PP
.I Idled
was written from a program called
.I Untamo,
which gets its name from the Finnish god of sleep and dreams.
.SH FILES
.TP
.B /etc/idled.cf
Configuration file which specifies how often idled is to wake up, and
exemptions to rules, etc.
There is no need to restart idled to change the configuration.
If changes are made to this file, idled will re-read the configuration
rules.
.TP
.B /var/log/idled.log
Log of when idled is started, killed, who it logs off and why, and any
errors it encounters.
.SH AVAILABILITY
.PP
The newest version of idled is available via anonymous ftp to
ftp.cs.hope.edu in /pub/idled
.PP
All comments and suggestions for idled would be greatly appreciated
and should be sent to crider@cs.hope.edu
.SH DIAGNOSTICS
Various \*(lqcouldn't open ...\*(rq error messages. Since idled
dissacociates itself from the invoking terminal, most of the errors
get put in the log file.
.SH SEE ALSO
idled.cf(5), utmp(5)
.SH BUGS
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.
.PP
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 console's keyboard--
and that is one <return> for each utmp line!).
.PP
If
.B idled
is started considerably after a user's 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 idled.c). I
left this because it would be somewhat messy to fix it, when
it will probably not have much effect anyway.
|
