Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

xlart(1) [debian man page]

xLart(1)						      General Commands Manual							  xLart(1)

NAME
xLart - interactive X interface to rlart(1) SYNOPSIS
xLart DESCRIPTION
xLart is an interactive X11-based interface to the rlart(1) off-line lart spooler. xLart uses the lartd - if lartd is not running when xLart is started, xLart will start it and send an autolart to the members of wheel (not including root). xLart utilises xfaces and Drag- and-Drop to allow playing admins to either drag lusers onto larts or vice versa. Points are accrued for each successful lart deployment, and scores written to /var/account/lart/interactive. xLart makes use of several basic larts, and as more points are accrued (or as the lusers become harder to lart) other, more capable larts are made available. The basic larts are: Filleting knife 10lb Sledgehammer Garrotte Beretta 9mm un-set concrete tommy gun Of course, since xlart is only distributed in source form, site-dependent larts may be designed, implemented and used by the relevant BOFH or sysmangler. The highest level of play also allows for the use of the atomic lart (lat and long must be specified, but some help is given by the pro- gram) and the psychological lart (old-style lobotomy, Electro-convulsive shock therapy, extreme aversion therapy and drug cocktails). The psychological lart needs to be used over several rounds, due to its non-instantaneous nature. The vanilla installation of xLart requires a configuration file list of larts to be added at certain point intervals. A slightly more interesting installation makes use of the xface library to provide that personal touch when larting lusers. The most interesting variant of xLart is to not only use xfaces but also to describe a building layout (similar to loderunner) with levels and interior descriptions. This variant allows several admins/BOFHen to play simultaneously, competing against each other to see how many lusers they can lart in a given time period (say until local police units arrive) or before ammunition runs out. FILES
/etc/lartcap - lart capability database /var/lib/lart/lusers/xface.<lusername> - xface for lusername /var/lib/lart/larts/<lartname>.ppm - small iconic image of lartname SEE ALSO
lartcap(5), lac(8), lartd(8) and rlart(1) BUGS
None found yet, but who really cares? AUTHORS
James McPherson GNU Utilities Aug 17, 1997 xLart(1)

Check Out this Related Man Page

LUSER(8)						      System Manager's Manual							  LUSER(8)

NAME
luser - process to control the clueless individuals who (mis)use computer systems, peripheral devices and system administrators. Word play on "loser" and "user". SYNOPSIS
luser [-d] [-g<level>] [-s] <lusername> DESCRIPTION
luser is the primary tool a system administrator uses to manage end-user requests. This powerful tool can actually cause the specified user to perform actions as specified by the flags. With no flags, luser deletes every running process owned by the specified <lusername>. OPTIONS
-d Disk reclamation mode. Remove all files in the home directory of <lusername>. -g<level> Grovel mode. Causes the specified luser to make an act of contrition to the sysadmin for past sins. The <level> indicates the sever- ity of the contrition: LEVEL 0 User makes a sincere apology and promises to never do it again. 1 User buys sysadmin a large quantity of sysadmin's favorite beverage. 2 User signs over ownership of his/her car to sysadmin. 3 User resigns from the company after writing a long letter of apology detailing his/her failings. 4 User commits ritual suicide by sucking on a power strip and grounding himself to a conduit. NOTES
Sysadmins are encouraged to use the -s option as a way to smarten up the world's user base. Use the -g option at level 4 outside the con- fines of the machine room. The more lusers that witness the act, the better. SEE ALSO
sysadmin(1) BUGS
Occasionally, the luser may survive the effects of luser -g4. In that event, a second invocation of the command will usually prove to be fatal. HISTORY
Written by Eric L. Pederson <eric@bofh.org.uk>. 25 September 1995 LUSER(8)
Man Page