sudo: unable to resolve host yourhostname No clue why sudo is doing that when running. Solution Check /etc/hosts You will probably find that it doesn't contain "yourhostname" for 127.0.0.1 Just update the hostname or add a field for your hostname like this: 127.0.0.1 yourhostname ........

The easiest way is to use SSHand DD or a combination of netcat. SSHwill be a little slower due to encryption but is the most secure way (on two older systems the average clone speed is about 40-50MB/s). This is also OS independent as it doesn't matter what the source OS is because you are literallly cloning the drive so you retain the partition table and settings. Clone HDD using SSH and DD........

Some guides still use the old Centos 6 style (do not use /etc/sysconfig/network). In Centos 7 the file is /etc/hostname echo "HOSTNAME=yourhostname.com" > /etc/hostname........

All Errors (CPanel does not report by domain, but puts everything in a single log which Ithink is a bit silly and annoying): /usr/local/apache/logs/error_log Access_Logs They are found within the home directory of the site user eg.: /home/admin/access-logs/yoursite.com MySQL Logs /var/lib/mysql/yourhostname.err........

This is e-mail notification to warn you that your hostname is setup improperly on your system. This is an annoying message and bug with Directadmin, my hostname is set correctly, why does it complain? To get of this message just run this command: /usr/local/directadmin/scripts/hostname.sh yourhostname.com........

mod_status is a great way to track down the source of high CPU usage and to find what vhost/script is the cause of it. It gives you a live view of bandwith usage, CPU usage, and memory usage broken down by domain/vhost and script/URI. Enable mod_status vi /etc/httpd/conf/httpd.conf ExtendedStatus On SetHandler server-status Order Deny,Allow Deny from all All........

Centos 5 Postfix and SPAMASSASSIN Tutorial yum install spamassassin chkconfig spamassassin on vi /etc/mail/spamassassin/local.cf ############## #required_hits 5 #report_safe 0 #rewrite_header Subject [SPAM] #5 is the least restrictive (means only the most obvious SPAM is caught. 0 is obviously the most restrictive/sensitive and would have lots of false positives require........

The first thing you need to remember is not to check from the same host/server itself. This is a silly mistake I made, the reason is that many mailservers and especially postfix are configured to allow relaying from the localhost/same host. If you do that you'll get a false positive. *Make sure you test from another host/system than the mail server itself! telnet yourmailserverhost.com 25 220 Courier (FreeBS........

understanding /etc/aliases *remember to apply changes you need to run "newaliases" after editing /etc/aliases one thing I don't get is that it doesn't allow you to specify the whole e-mail address on the left-hand side eg: yourfullemail@domain.com: someotheremail@domain.com postalias: warning: /etc/aliases, line 109: name must be local (if you try the above) It works more like this: your........