GSP
Quick Navigator

Search Site

Unix VPS
A - Starter
B - Basic
C - Preferred
D - Commercial
MPS - Dedicated
Previous VPSs
* Sign Up! *

Support
Contact Us
Online Help
Handbooks
Domain Status
Man Pages

FAQ
Virtual Servers
Pricing
Billing
Technical

Network
Facilities
Connectivity
Topology Map

Miscellaneous
Server Agreement
Year 2038
Credits
 

USA Flag

 

 

Man Pages


Manual Reference Pages  -  DOINKD (8)

NAME

doinkd - Idle terminal and multiple login monitor daemon.

CONTENTS

Synopsis
Description
Files
Availability
Diagnostics
See Also
Bugs

SYNOPSIS

doinkd [-f config_file ]

DESCRIPTION

doinkd wakes up at regular intervals and scans the system’s 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. doinkd then warns and logs out users based on a set of rules in its configuration file. doinkd is usually started from ’/etc/init.d’.

doinkd uses a configuration file, doinkd.cf, to find out how long a terminal must be unused to be considered “idle”, and which users, groups, terminals, or clusters of terminals are exempt from being logged out.

The path of the configuration file, which is compiled in, can be overriden by using the flag -f followed by the name of the configuration file to use (and path, if necessary).

doinkd was written from a program called Idled, which gets its name for obvious reasons. Idled was written from a program called Untamo, which gets its name from the Finnish god of sleep and dreams.

FILES

/usr/local/etc/doinkd/doinkd.cf
  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.
/var/log/doinkd.log
  Log of when doinkd is started, killed, who it logs off and why, and any errors it encounters.

AVAILABILITY

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

DIAGNOSTICS

Various “couldn’t open ...” error messages. Since doinkd dissacociates itself from the invoking terminal, most of the errors get put in the log file.

SEE ALSO

doinkd.cf(5), utmp(5)

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.

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!).

If doinkd 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 doinkd.c). I left this because it would be somewhat messy to fix it, when it will probably not have much effect anyway.

Search for    or go to Top of page |  Section 8 |  Main Index


--> DOINKD (8) May 30, 2006

Powered by GSP Visit the GSP FreeBSD Man Page Interface.
Output converted with manServer 1.07.