Date: Wed, 18 Dec 1996 04:58:23 -0700 From: bgingery@gtcs.com To: FreeBSD-gnats-submit@freebsd.org Cc: bgingery@gtcs.com, robbie@netcom.com Subject: ports/2241: Submission of eggdrop-1.0m port Message-ID: <199612181158.EAA07222@serv.gtcs.com> Resent-Message-ID: <199612181200.EAA03003@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 2241
>Category: ports
>Synopsis: eggdrop - A special TCL tool - an IRC Robotic Client.
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-ports
>State: open
>Class: change-request
>Submitter-Id: current-users
>Arrival-Date: Wed Dec 18 04:00:01 PST 1996
>Last-Modified:
>Originator: Bruce Gingery
>Organization:
Advanced Integrators, LC
>Release: FreeBSD 2.1-STABLE i386
>Environment:
FreeBSD 2.x.x+TCL7.x (Tk not required)
>Description:
Eggdrop is an irc-bot. v1.0m - 4 Dec 1996
FreeBSD port 18 Dec 1996
That is, it is a stand-alone pseudo-user that logs onto an
Internet Relay Chat network and can do just about anything that
a human user can do, and more. Eggdrop also contains its own
separate "botnet" with up to 64k channels and theoretically as
many linked bots as you wish. Eggdrop does not require ircII,
however the botuser should have SOME IRC client available on
some host somewhere.
Eggdrop can manage flood protection and ops control on one or
manyIRC channels. Has an optional DCC-Files area. Can be
re-compiled to do it's robotic things without attaching to any
IRC server (limbo), and can do anything that another tclsh can
do EXCEPT easily run as a user shell.
It is NOT a simple bot, but is well programmed. If you are used
to tcl, you'll enjoy making your eggie jump through hoops. Each
bot can connect to only one IRC server (hence one IRC net), but
can link to other bots, and as many as you'd care to run can run
from the same directory sharing SOME (or all) scripts. Each must
have its own run-time configuration script and unique name(s) and
TCP port (called a telnet port in the documentation, and indeed
it can be telneted to directly if configured to allow it.)
If you are NOT an accomplished TCL programmer, odds are that
you can make working bot with simple editing of the "FBSDbot"
or "lamestbot" example configuration files in a matter of minutes.
DIFFERENCES INSTALLING FreeBSD PORT OR PACKAGE
FROM OTHER (manual installation) of distribution.
The FreeBSD port has been extended from the original distribution
to allow root to do a system-wide install from which other users
can do individual installs (and conserve space and resources).
A sysadmin doing a "make" of the port has the option of doing
a full "make install" or merely invoking the "putegg" script
as is done on other systems. When a full make install (or install
from package) is done...
A system specific example "bot configuration" script is created
by the GNU-Configure script (which has been upgraded from the
original distribution). A manpage for the enhanced "putbot"
script is created and installed. The voluminous help files
are hard-linked by the enhanced putbot script, and those that
are user dependent instead of version dependent, are copied
to the bot's directory by the enhanced "putegg".
For "workstation" installs, eggies CAN be run from the actual
system install directory (usually /usr/share/eggdrop-1.0m),
with DCC files areas designated as /var/spool/eggdrop/*, and
softlinked from the install (as /usr/share/eggdrop-1.0m/dcc)
directory.
Installation of the bare distribution is a user-level activity.
Installation from the FreeBSD ports or packages creates an
installation appropriate for any of:
1. out-of-band by a user (identical to normal dist)
except that fetching of the distribution archive
is automated.
2. Shared system - with "putegg" used by each user
who is creating new bot(s). The installed "putegg"
is not the same, but functionally better for this
situation than the distribution putegg script.
3. Workstation, with bots either run from the install
directory, or from a "putegg" similar to #2.
SYSTEM IMPACT
The first eggie to run, made with tcl v7.6, may be expected to
require approximately 5M RAM (virtual), presuming that it is the
only libtcl*.so.* dependent application running. Additional
bots will generally take a hundred, to a few hundred k, depending
upon the number and complexity of scripts in use, number of bot-
users it is tracking (channel traffic), bans monitored, and other
minor consumption items. The CPU utilization will vary from
perhaps 10% down to .10%, depending upon channel traffic and number
of channels in which each bot participates. These figures are
all approximate, and your results may differ significantly.
It is NOT recommended to run a bot with DCC Files transfers
enabled from a dial-up or 56kbps connection, although quite
possible.
There is an enormous number of scripts in use with these bots.
Some are as simple as greeting a user when that person joins
an IRC channel, perhaps auto-op'ing a known user. Originally
written as a police-bot for #gayteens, it is also used as
a Bible concordance on some channels. This gives some indication
of its flexibility. Several eggies generally occupy #FreeBSD
on Undernet, along with the human denizens.
>How-To-Repeat:
The ports directory (including one patch file) has been
placed in ftp://ftp.freebsd.org/pub/FreeBSD/incoming/
as eggdrop-1.0m.tar.gz
N/A (ummm make install or make package :^&
>Fix:
N/A
>Audit-Trail:
>Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199612181158.EAA07222>