Debian

Want to support HowtoForge? Become a subscriber!
 

Setting Up ProFTPd + TLS On Debian Etch

Setting Up ProFTPd + TLS On Debian Etch

FTP is a very insecure protocol because all passwords and all data are transferred in clear text. By using TLS, the whole communication can be encrypted, thus making FTP much more secure. This article explains how to set up ProFTPd with TLS on a Debian Etch server.

Setting Up An NFS Server And Client On Debian Etch

Setting Up An NFS Server And Client On Debian Etch

This guide explains how to set up an NFS server and an NFS client on Debian Etch. NFS stands for Network File System; through NFS, a client can access (read, write) a remote share on an NFS server as if it was on the local hard disk.

How To Set Up Software RAID1 On A Running System (Incl. GRUB Configuration) (Debian Etch)

How To Set Up Software RAID1 On A Running System (Incl. GRUB Configuration) (Debian Etch)

This guide explains how to set up software RAID1 on an already running Debian Etch system. The GRUB bootloader will be configured in such a way that the system will still be able to boot if one of the hard drives fails (no matter which one).

Setting Up A Debian Packages Proxy With apt-cacher

Setting Up A Debian Packages Proxy With apt-cacher

There are many ways to install a Debian Linux but the most common is certainly to use the net-install 160MB CDROM. You can download it from http://www.debian.org/CD/netinst/. Booting up your PC from this CD, you will be capable of setting-up a basic Linux system; downloading updates, extra softwares and language support directly from the Internet. But using this method of installation on more than one PC in your LAN results in a massive waste of your precious bandwidth. Therefore, maybe you should consider using a cloning utility like “Sysimager”. But, as it is most likely that every computer will be slightly different one from another one, you should consider setting up a Debian Package Proxy as a long term solution.

How To Enable Multiple HTTPS Sites For One IP On Debian Etch Using TLS Extensions

How To Enable Multiple HTTPS Sites For One IP On Debian Etch Using TLS Extensions

This how-to is Debian specific but could be ported to other distributions since the concept is the same. In order to use TLS Extensions we have to patch and recompile apache2 and recompile OpenSSL with the enable-tlsext directive. Since TLS Extensions are relatively new, some internet browsers will not work so the apache2 server will deliver just the default site as http 1.0 does on an http 1.1 server.

Installing Openfire 3.3.3 & Spark 2.5.7 On Debian 4.0 Etch

Installing Openfire 3.3.3 & Spark 2.5.7 On Debian 4.0 Etch

This artivle explains how to install and use Openfire and Spark. Openfire (previously known as Wildfire Server) is a Jabber/XMPP server, and Spark is a Jabber/XMPP client; both are written in Java. Spark is an open source, cross-platform instant messaging client optimized for businesses and organizations.

Setting Up A High-Availability Load Balancer (With Failover and Session Support) With HAProxy/Heartbeat On Debian Etch

Setting Up A High-Availability Load Balancer (With Failover and Session Support) With HAProxy/Heartbeat On Debian Etch

This article explains how to set up a two-node load balancer in an active/passive configuration with HAProxy and heartbeat on Debian Etch. The load balancer sits between the user and two (or more) backend Apache web servers that hold the same content. Not only does the load balancer distribute the requests to the two backend Apache servers, it also checks the health of the backend servers. If one of them is down, all requests will automatically be redirected to the remaining backend server. In addition to that, the two load balancer nodes monitor each other using heartbeat, and if the master fails, the slave becomes the master, which means the users will not notice any disruption of the service. HAProxy is session-aware, which means you can use it with any web application that makes use of sessions (such as forums, shopping carts, etc.).

Setting Up A High-Availability Load Balancer (With Failover and Session Support) With Pound/Keepalived On Debian Etch

Setting Up A High-Availability Load Balancer (With Failover and Session Support) With Pound/Keepalived On Debian Etch

This article explains how to set up a two-node load balancer in an active/passive configuration with Pound and keepalived on Debian Etch. The load balancer sits between the user and two (or more) backend Apache web servers that hold the same content. Not only does the load balancer distribute the requests to the two backend Apache servers, it also checks the health of the backend servers. If one of them is down, all requests will automatically be redirected to the remaining backend server. In addition to that, the two load balancer nodes monitor each other using keepalived, and if the master fails, the slave becomes the master, which means the users will not notice any disruption of the service. Pound is session-aware, which means you can use it with any web application that makes use of sessions (such as forums, shopping carts, etc.).

Full Mail Server Solution w/ Virtual Domains & Users (Debian Etch, Postfix, Mysql, Dovecot, DSpam, ClamAV, Postgrey, RBL)

Full Mail Server Solution w/ Virtual Domains & Users (Debian Etch, Postfix, MySQL, DoveCot, DSpam, ClamAV, Postgrey, RBL)

This guide describes how to set up a full email solution in Debian Linux (all code is from Debian Etch).  I was asked to design a secure, scalable, portable solution for a small company.  While the guide references many 'servers', the company only had 4 physical machines, Xen was used to virtualize the entire solution.  That particular aspect of the system is not discussed in this guide, although I will try to get it into the next revision.

Merging Multiple Apache Access Logs Into One Overall Access Log

Merging Multiple Apache Access Logs Into One Overall Access Log

Let's assume you have a web application that runs of a cluster of Apache nodes. Each node generates its own Apache access log from which you can generate page view statistics with tools such as Webalizer or AWStats. Obviously you do not want to have page view statistics for each Apache node, but overall page view statistics. To achieve this, we must merge the access logs from each node into one overall access log that we can then feed into Webalizer or AWstats. There is a Perl script called logresolvemerge.pl (part of the AWStats package) that can do this for us.

first page
previous page
...
48
...
next page
last page