<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>linux on Home Page</title><link>https://ehsanakhgari.org/tags/linux/</link><description>Recent content in linux on Home Page</description><generator>Hugo -- gohugo.io</generator><language>en-ca</language><copyright>To the extent possible under law, Ehsan Akhgari has waived all copyright and related or neighboring rights to this website. This work is published from: Canada.</copyright><lastBuildDate>Sat, 24 May 2008 17:13:21 +0000</lastBuildDate><atom:link href="https://ehsanakhgari.org/tags/linux/index.xml" rel="self" type="application/rss+xml"/><item><title>How not to write an installer</title><link>https://ehsanakhgari.org/blog/2008-05-24/how-not-write-installer/</link><pubDate>Sat, 24 May 2008 17:13:21 +0000</pubDate><guid>https://ehsanakhgari.org/blog/2008-05-24/how-not-write-installer/</guid><description>OK, this is driving me crazy. ISPConfig is a great piece of software. It can manage your web sites, and related services (such as DNS, FTP, mail, etc.) well, and it handles the config files with pretty good care, and it rarely breaks. But, the installation experience is so twisted that I can't bear. And if I would only have to tolerate this at fresh installs, then I'd just try to live with it, but facing the same old problems once more each time I try to update the installation is way beyond acceptable.</description></item><item><title>Fail2ban only picking up the first ignore IP</title><link>https://ehsanakhgari.org/blog/2008-05-21/fail2ban-only-picking-first-ignore-ip/</link><pubDate>Wed, 21 May 2008 04:12:00 +0000</pubDate><guid>https://ehsanakhgari.org/blog/2008-05-21/fail2ban-only-picking-first-ignore-ip/</guid><description>Today I had this problem where Fail2ban was keeping on blacklisting an IP address, even though it was in the ignoreip list in /etc/fail2ban/jail.conf. After double-checking everything on the server, and googling desperately, I found out that up to version 0.8.2, Fail2ban had a bug which caused only the first IP in the ignoreip list to take effect. And guess what? Ubuntu versions before gutsy have older versions of Fail2ban. After a bit of digging, I found out the patch which had fixed the problem in 0.</description></item><item><title>libpam_foreground undefined symbol error on Ubuntu</title><link>https://ehsanakhgari.org/blog/2008-05-21/libpam_foreground-undefined-symbol-error-ubuntu/</link><pubDate>Wed, 21 May 2008 03:14:02 +0000</pubDate><guid>https://ehsanakhgari.org/blog/2008-05-21/libpam_foreground-undefined-symbol-error-ubuntu/</guid><description>If you happen to run Ubuntu Server (at least, up to version 7.04) and use the Courier POP3 or IMAP server, and you're watching your log files closely, you've seen error messages such as the below one in /var/log/syslog:
May 21 01:14:10 server4 authdaemond: PAM [dlerror: /lib/security/pam_foreground.so: undefined symbol: pam_set_data]
Many people have observed this problem. This happens because libpam-foreground.so has not been compiled with the right options. This library needs to be linked against libpam.</description></item><item><title>Linux server monitoring</title><link>https://ehsanakhgari.org/blog/2008-05-20/linux-server-monitoring/</link><pubDate>Tue, 20 May 2008 15:11:30 +0000</pubDate><guid>https://ehsanakhgari.org/blog/2008-05-20/linux-server-monitoring/</guid><description>Server monitoring is something server admins put off until, well, it's too late. Server admins have all experienced clients calling in to let them know that a service on their server is not working. This can be unfortunate and embarrassing at the very least. I thought I'd document a number of utilities I use to monitor Linux servers.
Snort. Snort is a NIDS and NIPS, and one of the most famous network security tools.</description></item></channel></rss>