.nr X .TH IQS "Apr 15, 1997" .\" Copyright (c) 1997 Dan Stromberg .SH NAME IQS \- Implicit Queuing System .SH SYNOPSIS .B IQS [ .B \-v ] [ .B \-n processes ] .SH DESCRIPTION IQS manages cpu-hogging jobs. A coarse-grained round-robin schedling is implemented using SIGSTOP and SIGCONT, for batch processes. No "qsub" analog (ala NQS and DQS) is available, or needed; IQS automatically detects which jobs it should manage. .LP The .B \-v option makes IQS say what it's doing. .LP .B \-n processes indicates how many processes should be run concurrently. This doesn't necessarily have to be equal to the number of processors on the machine. .SH EXAMPLES .TP .B IQS & Starts IQS for a single-processor machine. .TP .B IQS -v -n 4 Starts IQS verbosely, in the foreground, for a 4-cpu machine. .LP .SH FILES .TP .B /var/IQS/exempt-programs is a file containing names of programs not to manage. Format is one program name per line. netscape is a common program that should be exempted. If you use this file, users may figure out that they can rename their batch programs to "netscape". The best way to contentd with this is policy. .TP .B /var/IQS/exempt-users is a file containing names of users whose processes should not be managed. Format is one username per line. Some administrators may want to always exempt root, although few people run such CPU-hogging programs as root. .TP .B /var/IQS/managed lists pids of managed processes, one pid per line. Unlike exempt-programs and exempt-users, this file is automatically generated. However, you can add pids and kill -HUP IQS (if you hurry, before IQS writes the pids again). .SH SIGNALS .TP .B SIGINTR Exits gracefully, allowing managed processes to run freely. .TP .B SIGTERM Same as SIGINTR. .TP .B SIGHUP Causes /var/IQS/managed to be re-read. .SH BUGS .LP If a lot of CPU-hungry processes are started all at once, IQS is unlikely to manage them - because each will consume a small enough percentage of the CPU, that they do not look CPU-hungry. .LP kill -9 <IQS pid> leaves processes suspended.