CentOS 7 or newer is needed because of the C++ standards being used, and older CentOS not having the required compilers for those standards. These instructions work properly to create a basic ZNC installation. Note that these instructions do utilize the EPEL repository in order to get all the necessary build dependencies (and there's a lot of them). If you really wish to build from source, then please follow the instructions here, written by Thomas Ward. Sudo systemctl start znc # or enable if you want it to autostartīuild from Source: CentOS 7+ only Sudo -u znc znc -makeconf # this creates /var/lib/znc/.znc Once installed you can configure znc by running: Once you have EPEL installed (or are on Fedora), execute:
Install tcl package centos install#
If using RHEL install the EPEL repository by downloading the appropriate package linked on EPEL's website. Note that sometimes these build-depedencies are outdated and won't work with the current version of ZNC.įedora/CentOS/Red Hat Enterprise Linux įedora has znc packaged in it's main repository and their Extra Packages for Enterprise Linux (EPEL) repository provides them for CentOS/RHEL. To install build dependencies automatically. If you want to build znc from source to get a newer version than Debian provides, you may need the following packages: If you are having issues with ZNC from your Debian package manager (prior to Sid), it is recommended to uninstall that package and build from source, or use the third-party repository (noted below).ĭebian provides ZNC packages which may be installed using (stretch/stable, buster/testing, sid)ĭebian Jessie LTS backports apt -t jessie-backports install znc
There could be security issues and even bugs in the code. Prior to Debian Sid (Unstable) including Wheezy the ZNC packages included in the repositories for those older releases are extremely old. If you want to test great new features (and bugs!), unstable ZNC image is here. ZNC is available as an image in Docker Hub, and can be downloaded with:įollow the link above for additional instructions. See the FAQ page if you encounter problems. It does not automatically make an init.d service for itself (which can be done by following the instructions to running ZNC as a system daemon) nor does it need to be run in screen or something similar. ZNC is run by just executing znc under the dedicated znc user, at which stage it goes to background. You should create a dedicated non root user to run znc under. This config is stored in ~/.znc under the user you run it as. Once you have installed znc, you can use znc -makeconf to make a configuration file for ZNC. Please note that compiling can take 5-10 minutes or more. (if you are on a dedicated server and your CPU has more than one core, you can use make -jX where X is the number of CPU cores to speed up compilation) (use ccmake or cmake-gui to see other configure options) DCMAKE_INSTALL_PREFIX="$HOME/.local" if you don't want a system wide installation or simply don't have root access use cmake -DOPENSSL_ROOT_DIR=/path/to/openssl if you have a non-standard SSL path) On Debian/Ubuntu this is called libssl-dev, on CentOS/Fedora/Red Hat it's openssl-devel, and on openSUSE it's libopenssl-devel.Ī good way to install this and other dependencies is the build dependency feature of package managers ( apt-get build-dep / yum-builddep / zypper source-install -build-deps-only). If you want to compile ZNC with OpenSSL support, you need the OpenSSL development package. Official source tarballs can be found here. Beware that this might have more bugs, more features, be a little unstable and eat your first born. Read the git page if you want to get the current development version.
0 kommentar(er)
