Generate a random password in bash
Here’s a quickie that Feliscimo sent me:
-
< /dev/urandom tr -dc _A-Z-a-z-0-9 | head -c8
Here’s a quickie that Feliscimo sent me:
The documentation is per http://awstats.sourceforge.net/docs/awstats_setup.html
Here’s quick HOWTO, where I assume you have installed awstats using apt-get or rpm:
Copy the file /etc/awstats/awstats-dist.conf to /etc/awstats/awstats.mydomain.com.conf and changed the domain name there to fit the new site.
Then run the following command:
[root@funinc ~]# perl /usr/local/awstats/wwwroot/cgi-bin/awstats.pl -config=mydomain.com -update
Awstats creates a new set of files for the new site in its database.
Added the following line to your crontab file:
12 00 * * * perl /usr/local/awstats/wwwroot/cgi-bin/awstats.pl -update -config=mydomain.com
basically this will tell awstats to generate a new set of reports for the mydomain.com site daily (at 12 noon!)
Basically that’s it, go to http://mydomain.com/awstats/awstats.pl?config=mydomain.com
And I found the answer in this post:
http://www.irbs.net/internet/postfix/0406/2819.html
Basically it says:
To mail to IP address, use IP literals, such as user@[72.249.191.48]
You might also what to look at the following post for related info as well:
http://www.cyberciti.biz/faq/postfix-receive-mail-on-specific-network-interfaces/
from this blog post
If you’re using apt to manage your software installations on a redhat based machine, especially to make use of the rpmforge repository and tools, you might get this error.
Description:
I start apt-get update. After a while, it gets to the apt.sw.be and hangs at a certain %. You cannot stop it as it hogs the CPU. (hint. login using console and kill it?)
The problem seems to be related to the /etc/apt/sources.list.d/rpmforge.list file. Simply comment out the repomd line and let it use the rpm line as follows:
rpm http://apt.sw.be redhat/el$(VERSION)/en/$(ARCH) dag
#repomd http://apt.sw.be redhat/el$(VERSION)/en/$(ARCH)/dag
This seems to affect rhel4/fedora servers.
I’ve always felt it was a hassle to gather the data needed for tuning mysql, let alone interpret it. Here’s a great tool to do just that: the MySQL Performance Tuning Primer Script. From the page:
Currently it handles recomendations for the following:
Slow Query Log Max Connections Worker Threads Key Buffer Query Cache Sort Buffer Joins Temp Tables Table (Open & Definition) Cache Table Locking Table Scans (read_buffer) Innodb Status
Setting up the latest (as of June 2008) php on a RHEL4 server (the same would work on RHEL5 or CentOS as well):