slackbuilds_ponce/network/znc
2010-05-13 13:25:08 +02:00
..
doinst.sh
rc.znc network/znc: Updated for version 0.076. 2010-05-13 13:25:08 +02:00
README network/znc: Updated for version 0.076. 2010-05-13 13:25:08 +02:00
README.SBo network/znc: Updated for version 0.076. 2010-05-13 13:25:08 +02:00
README.SLACKWARE network/znc: Updated for version 0.076 2010-05-13 00:38:51 +02:00
slack-desc network/znc: Updated for version 0.076. 2010-05-13 13:25:08 +02:00
znc.info network/znc: Updated for version 0.076. 2010-05-13 13:25:08 +02:00
znc.SlackBuild network/znc: Updated for version 0.076. 2010-05-13 13:25:08 +02:00

ZNC is an advanced IRC bouncer

ZNC will remain connected to an IPv4 or IPv6 IRC server even while you
are offline. You can reattach your client at a later time and catch up
with what happened while you were gone via the history buffer. You can
add additional users under one running process, useful for public shells
that limit background processes. ZNC also supports the dynamic loading
of C++ and Perl modules.

The SlackBuild file for ZNC includes support for OpenSSL connections
to IRC servers.  If you do not wish to include OpenSSL support in ZNC, 
simply run the build script like this:
	WITH_SSL=no ./znc.SlackBuild

IPv6 support is also enabled by default; to disable it, run the script as:
	WITH_IPV6=no ./znc.SlackBuild

New since version 0.074 is the ability to use the 'c-ares' library. This
package is available on SBo and will slightly increase performance
by being able to do asynchronous DNS requests. By default this option
is off, to enable it run the script as:
WITH_CARES=yes ./znc.SlackBuild

This is intended to be run as a nonprivileged user - by default, the
build script uses "znc" as the user.  If you wish to change it, e.g. 
to use the "nobody" user, then run the script as follows:
	ZNC_USER=nobody ./znc.SlackBuild

See README.SBo for configuration information.