UNIX daemon for limiting user time on the machine.
d03d713004
There are several lines in the code which cause GCC to warn the user about undefined behaviour. Most of these are potential buffer overflow problems. Which come from either overwriting a buffer which may be too small for a given input, or writing to, or from, a string not guaranteed to be null-terminated, such as any of the char[] fields in a utmp struct. Almost all come from an improper usage of strcmp or strncmp or similar. |
||
|---|---|---|
| debian | ||
| dump_wtmp.c | ||
| Makefile | ||
| README | ||
| timeoutd.8 | ||
| timeoutd.c | ||
| timeouts | ||
| timeouts.5 | ||
| VERSION | ||
TIMEOUTD 1.5 by Shane Alderton Timeoutd is a programme which allows you to control the following characteristics on a user by user and/or group by group basis for each tty on your system: - maximum idle time - maximum time per session - maximum time per day - times when people can/can't login on specific ttys To build timeoutd, you should make any changes to the makefile for your preferred compilation options, then simply: make The next step is to install a timeouts file in /etc specifying the parameters for each line/user/group combination. You can use the sample file provided in the distribution as a starting point after reading the timeoutd.8 and timeouts.5 man pages. Once you have installed the timeouts file in /etc, you can type: make install to install the timeoutd binaries and man pages. Then it is just a matter of running /usr/sbin/timeoutd. You may want to add a line to your /etc/rc or /etc/rc.local (or whatever) to run timeoutd at boot time. If you wish, you can also modify your login programme to have timeoutd run at login time to check whether each user is allowed to login or not. Otherwise, users who are not allowed to login will be logged off within 1 minute of logging in. Another (albeit less certain) way of doing this is to put the following line in /etc/profile near the top of the file: /usr/etc/timeoutd `whoami` `basename \`tty\`` || exit Please send bugs, comments, suggestions to: shanea@bigpond.net.au (Shane Alderton)