ku README
=========

To compile, just type: ./configure ; make install
If it doesn't compile, let me know.  Note this is only for Linux.


CONFIGURATION
=============

ku specific configure options:

	--with-message='your message here'

		To change the default kill message, give configure the
		--with-message option.  Please note, you must enclose
		the whole message in quotes, so the shell will see it
		as 1 (one) argument.  Also, you may need to escape any
		extra quotes etc.
	
		e.g. - ./configure --with-message="%Y killed %l at %T"


	--disable-header

		The default is 'yes' for the header.  If it bugs you
		issue configure the --disable-header option to turn
		it off.

		e.g. - ./configure --disable-header


KILL MESSAGES
=============

ku will accept kill messages in the following formats, and looks for
them in this order:

	command line:

		# ku -avhbp -m "%l just got killed by %Y"


	enviromental variable:

		# export KU_MESSAGE="%l just got killed by %Y"
		# ku -avhbpm


	ku message file (/etc/ku.msg):

		# cat /etc/ku.msg
		%l just got killed by %Y
		# ku -avhbpm


DESCRIPTION
===========

ku (killuser) is a utmp based shell admin utility similar to Slay. ku was 
written in C in hopes for an increase in program speed, efficiency, and 
availability of more options, as opposed to other shell/perl scripts that 
are around. It was designed to ease the pain of admins who use ps and kill 
to disconnect users from their server. A wide range of options are offered 
to satisfy most any possible condition associated with a shell login.


EXPLANATION
===========

ku tries to prove each option on the command line to be TRUE or FALSE, if 
ku found even one of the options to be FALSE, then ku will skip that shell
/user, and continue until all users/shells have been examined. This type of 
system allows for many options to be issued together, allowing greater flex-
ibility in what shells are terminated, and what shells are not.


LIMITATIONS
===========
When using the --message option anywhere but at the end of the command line, 
ku will take everything issued after the --message option as a part of the 
literal kill  message so if you issued 'ku -m -avh', ku would think the 
message it was supposed to print was '-avh'. this  problem stems from the 
way ku was coded not require quotation marks around the whole message to 
make get_opt_only() accept the whole message as the single ooppttaarrgg..  
Instead ku was coded to parse each argv[x] AFTER the --message option was 
issued, as part of the message.

   FIX
   ===
        usage quotation marks around the message body, or make sure that the
        --message option is the last option issued. ie:
        ku -m "%l smells like chicken" -avh
     or:
        ku -avh -m %l smells like chicken


AUTHORS
=======

ku was orginally started by Nathan Benson (phuzz@phactor.org) but is now
mainly worked on by Tomi Bendixen (issue@technotronic.com). Many thanks goes
to Nathan for his time spent working on ku.


BUGS
====

Please report bugs to issue@technotronic.com, or phuzz@phactor.org
