Linux Conquering Cloud

Friday, April 5, 2013

creation of cpanel accounts through command line

root@V-6862 [~]# vi /scripts/createacct
root@V-6862 [~]# /usr/local/cpanel/bin/wwwacct
Please use the following syntax:
wwwacct <domain> <user> <pass> <quota> <cpmod[advanced/?]> <ip[y/n]> <cgi[y/n]> <frontpage[y/n]> <maxftp> <maxsql> <maxpop> <maxlst> <maxsub> <bwlimit> <hasshell[y]/[n]> <owner> <plan> <maxpark> <maxaddon> <featurelist> <contactemail> <use_registered_nameservers> <language>

yes | /scripts/createacct keralainindia.asia kerala india

Tuesday, April 2, 2013

Understanding WordPress Permalinks

Permalinks are the permanent URLs to your individual blog posts, pages, categories, and other content on your WordPress site. Think of them as the address for each piece of content. By default, WordPress might use "ugly" URLs that look like this:

domain.com/?p=123

This means a post with the ID number 123. While functional, these URLs aren't very user-friendly or good for search engines.

WHY ARE FRIENDLY PERMALINKS IMPORTANT?

Readable permalinks offer several benefits:

Improved User Experience: Visitors can easily understand what a link is about just by looking at the URL.
Better Search Engine Optimization (SEO): Search engines prefer descriptive URLs as they provide clues about your content.
Easier Sharing: Clean URLs are simpler to share on social media or in emails.

Instead of domain.com/?p=123, a friendly permalink might look like:

domain.com/name-of-post

FIXING 404 ERRORS AND SETTING UP PERMALINKS

Occasionally, you might encounter 404 "page not found" errors on your WordPress site. This can sometimes be resolved by refreshing your permalink settings. Even if you're not seeing errors, it's good practice to ensure your permalinks are set up for readability.

Here's how to configure your permalinks:

Access Your WordPress Admin: Log in to your WordPress dashboard.
Navigate to Settings: In the left-hand menu, click on "Settings."
Go to Permalinks: Under "Settings," click on "Permalinks."
Choose a Structure: On the Permalinks settings page, you'll see several options for your URL structure.
- To get a clean, post-name-based URL, select the "Custom Structure" option.
- In the box next to "Custom Structure," enter: /%postname%/
Save Changes: Click the "Save Changes" button at the bottom of the page.

Monday, April 1, 2013

Error github: github.com [0: 207.97.227.239]: errno = Connection timed out fatal: unable to connect a socket (Connection timed out)

Error github: github.com [0: 207.97.227.239]: errno = Connection timed out fatal: unable to connect a socket (Connection timed out)

git clone -b 6.1.1 git://github.com/wgm/cerb6.git
And got this result:
Cloning into 'cerb6'...
fatal: unable to connect to github.com:
github.com[0: 207.97.227.239]: errno=Connection timed out

This error just happens because you have blocked port 9418 on the proxy just enable it and runs smoothly gitbub

installing git for single user

cd ~
wget http://git-core.googlecode.com/files/git-1.7.10.1.tar.gz
tar zxvf git-1.7.10.1.tar.gz
cd git-1.7.10.1
./configure --prefix=/home/$USER
make
make install
echo 'PATH=$PATH:$HOME/bin' >> $HOME/.bashrc
source $HOME/.bashrc

named-checkzone and named-checkconf command syntax

named-checkzone {zonename} {filename}
Where,

zonename : The domain name of the zone being checked.

filename : The name of the zone file.

How do I check my zone file configuration for errors?

Use named-checkzone to check the zone files as follows:
named-checkzone nixcraft.com /var/named/zone.nixcraft.com
Output:

OK

If you see "OK" as result, the zone file is properly configured and you can restart bind name server.

How do I check my bind configuration for errors?

Simply run command as follows:
# named-checkconf /etc/named.conf
You may want to chroot to directory so that include directives in the configuration file are processed as if run by a similarly chrooted named:
# named-checkconf -t /var/named/chroot /etc/named.conf
If there is no output, the configuration is considered correct and you can safely restart or reload bind configuration file. If there is an error it will be displayed on screen:
# named-checkconf /etc/named.conf

Kloxo important file location

ROUND CUBE

/home/kloxo/httpd/webmail/roundcube/logs/errors

Mail

/var/log/kloxo/mailog

/var/log/kloxo/courier

/tmp/horde.log

/var/log/kloxo/smtp.log

/usr/local/lxlabs/kloxo/mail_send

/var/qmail/control/me

/var/qmail/control/rcpthosts

/var/qmail/control/defaultdomain

/var/qmail/control/defaulthost

/var/qmail/control/locals

/var/qmail/users/assign

Show the users assigned

FTP

/var/log/kloxo/pureftpd.log

/var/run/pure-ftpd.pid

SSH

/var/log/secure

DNS

/usr/local/lxlabs/kloxo/log/dns_log

Database

/var/log/mysqld.log

/usr/local/lxlabs/kloxo/log/database

SSL

/var/log/httpd/ssl_error_log

File System

/usr/local/lxlabs/kloxo/log/filesys

/usr/local/lxlabs/kloxo/log/nonfilesys

/usr/local/lxlabs/kloxo/log/remove_oldfile

Bandwitdh

/usr/local/lxlabs/kloxo/log/get_traffic

Cron

/usr/local/lxlabs/kloxo/log/cron_error

/usr/local/lxlabs/kloxo/log/cron_exec

/var/spool/cron/

Store the custom crontab per name user inside

Admin

/usr/local/lxlabs/kloxo/log/admin_error

/usr/local/lxlabs/kloxo/log/login_success

/usr/local/lxlabs/kloxo/log/message

/usr/local/lxlabs/kloxo/log/user_cmd

/usr/local/lxlabs/kloxo/log/access_log

Log every access

Internal

/usr/local/lxlabs/kloxo/log/shell_exec

/usr/local/lxlabs/kloxo/log/shell_error

/usr/local/lxlabs/kloxo/log/other_cmd

/usr/local/lxlabs/kloxo/log/syncserveriherit

/usr/local/lxlabs/kloxo/log/ajax

/usr/local/lxlabs/kloxo/log/error

General error log

/usr/local/lxlabs/kloxo/log/update

/usr/local/lxlabs/kloxo/log/watchdog

/usr/local/lxlabs/kloxo/log/security

/usr/local/lxlabs/kloxo/log/run_stats

/usr/local/lxlabs/kloxo/log/redirect_error

PHP

/usr/local/lxlabs/ext/php/error.log

/usr/local/lxlabs/kloxo/httpdocs/.php.err

Lighttpd

/home/kloxo/httpd/lighttpd/error.log

/home/kloxo/httpd/lighttpd/ligh.log

/usr/local/lxlabs/kloxo/log/lighttpd_error.log

Apache

/var/log/httpd/error_log

Others

/var/log/messages

exiqgrep in detail

Exim includes a utility that is quite nice for grepping through the queue, called exiqgrep. Learn it. Know it. Live it. If you’re not using this, and if you’re not familiar with the various flags it uses, you’re probably doing things the hard way, like piping `exim -bp` into awk, grep, cut, or `wc -l`. Don’t make life harder than it already is.

First, various flags that control what messages are matched. These can be combined to come up with a very particular search.

Use -f to search the queue for messages from a specific sender:

root@localhost# exiqgrep -f [luser]@domain

Use -r to search the queue for messages for a specific recipient/domain:

root@localhost# exiqgrep -r [luser]@domain

Use -o to print messages older than the specified number of seconds. For example, messages older than 1 day:

root@localhost# exiqgrep -o 86400 [...]

Use -y to print messages that are younger than the specified number of seconds. For example, messages less than an hour old:

root@localhost# exiqgrep -y 3600 [...]

Use -s to match the size of a message with a regex. For example, 700-799 bytes:

root@localhost# exiqgrep -s '^7..$' [...]

Use -z to match only frozen messages, or -x to match only unfrozen messages.

There are also a few flags that control the display of the output.

Use -i to print just the message-id as a result of one of the above two searches:

root@localhost# exiqgrep -i [ -r | -f ] ...

Use -c to print a count of messages matching one of the above searches:

root@localhost# exiqgrep -c ...

Print just the message-id of the entire queue:

root@localhost# exiqgrep -i

MANAGING THE QUEUE

The main exim binary (/usr/sbin/exim) is used with various flags to make things happen to messages in the queue. Most of these require one or more message-IDs to be specified in the command line, which is where `exiqgrep -i` as described above really comes in handy.

Start a queue run:

root@localhost# exim -q -v

Start a queue run for just local deliveries:

root@localhost# exim -ql -v

Remove a message from the queue:

root@localhost# exim -Mrm <message-id> [ <message-id> ... ]

Freeze a message:

root@localhost# exim -Mf <message-id> [ <message-id> ... ]

Thaw a message:

root@localhost# exim -Mt <message-id> [ <message-id> ... ]

Deliver a message, whether it’s frozen or not, whether the retry time has been reached or not:

root@localhost# exim -M <message-id> [ <message-id> ... ]

Deliver a message, but only if the retry time has been reached:

root@localhost# exim -Mc <message-id> [ <message-id> ... ]

Force a message to fail and bounce as “cancelled by administrator”:

root@localhost# exim -Mg <message-id> [ <message-id> ... ]

Remove all frozen messages:

root@localhost# exiqgrep -z -i | xargs exim -Mrm

Remove all messages older than five days (86400 * 5 = 432000 seconds):

root@localhost# exiqgrep -o 432000 -i | xargs exim -Mrm

Freeze all queued mail from a given sender:

root@localhost# exiqgrep -i -f luser@example.tld | xargs exim -Mf

View a message’s headers:

root@localhost# exim -Mvh <message-id>

View a message’s body:

root@localhost# exim -Mvb <message-id>

View a message’s logs:

root@localhost# exim -Mvl <message-id>

Add a recipient to a message:

root@localhost# exim -Mar <message-id> <address> [ <address> ... ]

Edit the sender of a message:

root@localhost# exim -Mes <message-id> <address>

Pages