autolog(8) [linux man page]
AUTOLOG(8) System Manager's Manual AUTOLOG(8) NAME
autolog - Log out idle users SYNOPSIS
autolog [ options ] DESCRIPTION
The program reads the utmp file, entry by entry. The username for each 'user process' is compared to the entries in the configuration file (see autolog.conf(5) ). The first entry to match both the name, the group, and the tty line of the process will be used to conduct the automatic logout. CALL
/etc/init.d/autolog start or autolog to run this program in daemon-mode autolog -o to run this program as "ordinary" program. Keep in mind: Also when running as ordinary program, it will stay in memory until all its jobs are done. OPTIONS
-a (all processes) Print information on ALL utmp entries--not just user processes. -d (debug mode) This is helpful in setting up your configuration file. The program runs in foreground rather than forking and it prints out verbose messages about what it is doing. -n (nokill) Use this to prevent autolog from actually "killing" anyone. Use -d and -n together when setting up a new configuration file. ( This will not affect killing of lost processes. ) -o (ordinary) Use this to run this program as ordinary program, not as daemon. Program will end, when its job is done. In this case, some data is kept in "/var/lib/autolog/autolog.data". This is read, when the program is called again. -f config_file_name Use this to override the default: "/etc/autolog.conf" -l log_file_name Use this to override the default: "/var/log/autolog.log". Note that if this file doesn't exist, no logging will happen. Create the file (with touch) to enable logging. -t idle_time Use this to override the internal default idle time (minutes) -g grace_period Use this to override the internal default grace period (seconds) -m yes/no Use this to override the internal mailing switch. If "yes" the program will send mail to the users right after killing them. -c yes/no Use this to override the internal "pre-clear" switch. If "yes" the program will clear the terminal screen before warning the user. -w yes/no Do timeouts based on total session time--not idle time. (hard) -l yes/no If set to "yes" activities will be written to the logfile if present. AUTHOR
Kyle Bateman <kyle@actarg.com> (autolog 0.35), Carsten Juerges <juerges@cip-bau.uni-hannover.de> (autolog 0.40) This manual page was modified for Debian by Paul Telford <pxt@debian.org> Linux Administrative Utilities AUTOLOG(8)
Check Out this Related Man Page
ionice(1) General Commands Manual ionice(1) NAME
ionice - get/set program io scheduling class and priority SYNOPSIS
ionice [[-c class] [-n classdata] [-t]] -p PID [PID]... ionice [-c class] [-n classdata] [-t] COMMAND [ARG]... DESCRIPTION
This program sets or gets the io scheduling class and priority for a program. If no arguments or just -p is given, ionice will query the current io scheduling class and priority for that process. As of this writing, a process can be in one of three scheduling classes: Idle A program running with idle io priority will only get disk time when no other program has asked for disk io for a defined grace period. The impact of idle io processes on normal system activity should be zero. This scheduling class does not take a priority argument. Presently, this scheduling class is permitted for an ordinary user (since kernel 2.6.25). Best effort This is the effective scheduling class for any process that has not asked for a specific io priority. This class takes a priority argument from 0-7, with lower number being higher priority. Programs running at the same best effort priority are served in a round- robin fashion. Note that before kernel 2.6.26 a process that has not asked for an io priority formally uses "none" as scheduling class, but the io scheduler will treat such processes as if it were in the best effort class. The priority within the best effort class will be dynam- ically derived from the cpu nice level of the process: io_priority = (cpu_nice + 20) / 5. For kernels after 2.6.26 with CFQ io scheduler a process that has not asked for an io priority inherits CPU scheduling class. The io priority is derived from the cpu nice level of the process (same as before kernel 2.6.26). Real time The RT scheduling class is given first access to the disk, regardless of what else is going on in the system. Thus the RT class needs to be used with some care, as it can starve other processes. As with the best effort class, 8 priority levels are defined denoting how big a time slice a given process will receive on each scheduling window. This scheduling class is not permitted for an ordinary (i.e., non-root) user. OPTIONS
-c class The scheduling class. 0 for none, 1 for real time, 2 for best-effort, 3 for idle. -n classdata The scheduling class data. This defines the class data, if the class accepts an argument. For real time and best-effort, 0-7 is valid data. -p pid Pass in process PID(s) to view or change already running processes. If this argument is not given, ionice will run the listed pro- gram with the given parameters. -t Ignore failure to set requested priority. If COMMAND or PID(s) is specified, run it even in case it was not possible to set desired scheduling priority, what can happen due to insufficient privileges or old kernel version. EXAMPLES
# ionice -c 3 -p 89 Sets process with PID 89 as an idle io process. # ionice -c 2 -n 0 bash Runs 'bash' as a best-effort program with highest priority. # ionice -p 89 91 Prints the class and priority of the processes with PID 89 and 91. NOTES
Linux supports io scheduling priorities and classes since 2.6.13 with the CFQ io scheduler. AUTHORS
Jens Axboe <jens@axboe.dk> AVAILABILITY
The ionice command is part of the util-linux package and is available from ftp://ftp.kernel.org/pub/linux/utils/util-linux/. ionice August 2005 ionice(1)