split -l 50000 dump.csv newdump

Which will split the text file in output files of 50000 lines each. This is another way to split a file and is mostly used for text files like logs, sql dumps, csv files, etc.

Examples marked with • are valid/safe to paste without modification into a terminal, so you may want to keep a terminal window open while reading this so you can cut & paste.
All these commands have been tested both on Fedora and Ubuntu.

Open file in bash
vi ~/.bashrc

Add following line to .bashrc
alias ls="ls -al --color"

NOTE: log off and login (or run bash) to see the result

Replace a colors

By default CentOS/RHEL show directorys in ls listing in dark green. With dark color it’s difficult to read directory names.


cp /etc/DIR_COLORS ~/.dir_colors
vi ~/.dir_colors

FIND: DIR 01;34 # directory
REPLACE WITH: DIR 01;33 # directory

NOTE: log off and login (or run bash) to see the result.

Everything was tested  CentOS, Fedora, and Redhat.

cat /etc/*release*

or

specific for centos/redhat: cat /etc/redhat-release

svn st |grep -e ^\? -e ^I | awk '{print $2}'xargs rm

Note 1: Use rm -rf  to delete directions and files without questions  svn st |grep -e ^\? -e ^I | awk ‘{print $2}’xargs rm -rf
Note 2: awk fix a problem with white spaces.

ls -al –color /etc

Open the .bashrc file with your favorite text editor.
For example, you could type vi /root/.bashrc at the command line to open the file.

Under the line “# User specific aliases and functions” type:

alias ls=”ls -alh –color”
alias ll=”ls -alh –color”

Make sure to write your changes to the file and save them. The changes will not take effect until you close your terminal/session window and re-open a new terminal again.

here solution:

1. Download your client certificate from thawte (.crt file thawte sent)
2. Download the primary and secondary intermediate CAs
3. Combine the 3 certificates into one file, with your certificate first, then the primary and secondary intermediate certificates.
4. Add: ssl_verify_depth 3; to your configuration file
5. Restart nginx (/etc/init.d/nginx restart)

So in the end, your nginx configuration file should look like the following:

ssl_certificate         /path/to/certificate.bundle.cert;
ssl_certificate_key     /path/to/private.key;
ssl_verify_depth 3;

Now your browser should say that the certificate was issues by Thawte DV SSL CA.
Test it by visiting https://www.ssllabs.com/ssldb/

Mails are *not* deleted from the queue! They are only stored, temporarily, in $qmail-queue/yanked/, where you can view them individually and restore them back to the queue manually. There is currently no support for restoring them automatically.

By default, Qmail-Remove assumes that your Qmail queue is stored in /var/qmail/queue, but this can be changed with a command line option. Similarly, Qmail-Remove assumes that your queue “split” is 23 by default, among other things.

If you want to check your qmail queue using the following command

# /var/qmail/bin/qmail-qstat

Output looks like

messages in queue: 567154
messages in queue but not yet preprocessed: 3

Install Qmail-Remove

First you need to download latest version from here current version is Qmail-Remove 0.95

Download using the following command

#wget http://www.linuxmagic.com/opensource…remove-.tar.gz

Now you have qmail-remove-0.95.tar.gz file and now you need to extract using the following command

#tar -zxvf qmail-remove-.tar.gz

Now you should have qmail-remove-0.95 folder go in to the directory and run the following commands

#make

#make install

This will complete the installation.

Now you need to create a directory named “yanked” in the qmail queue directory you intend to use before using this program.

#mkdir /var/qmail/queue/yanked

Examples for qmail-remove

Before doing any thing related to qmail queue you need to stop the qmail service using the following command:

#/etc/init.d/qmail stop

To delete mails from Que,

#qmail-remove -r -p

# qmail-remove -r -p mega.pack.com

This will remove all emails in queue with “mega.pack.com” in it and place it in /var/qmail/queue/yanked folder.

• Add following rules to your httpd.conf

  <IfModule mod_rewrite.c>
  RewriteLog "/var/log/httpd/rewrite.log"
  RewriteLogLevel 3
  </IfModule>
  

  to the appropriate VirtualHost section.

• Restart Apache by command in your shell (as root)
  apachectl graceful

Note: You’re not going to be able to turn above rules with shared hosting, they can’t be used in .htaccess by default. But you could ask your server-administrator to set AllowOverride to “All” instead “None”. And you will available to add above rules to .htaccess.

There a trick that’s helps debug mod_rewrite on shared hosting even AllowOverride is “None”.
Basically what you do is dump some of the info that mod_rewrite is using back out into the headers then use the Firebug or LiveHTTP Headers extensions in Firefox to watch the headers and read your debug info.
Add following rules to .htaccess:

RewriteCond %{QUERY_STRING} !vardump
RewriteRule (.*) http://www.your_website.com/$1?vardump&thereq=%{THE_REQUEST}&reqhost=%{HTTP_HOST} [R=301,L,QSA]

to dump, for example, the THE_REQUEST and HTTP_HOST into request variables.
The R=301 does a 301 redirect instead of a rewrite – this is key. A redirect sends information back to the browser but a rewrite happens all inside the server.

Internally rewrite .example.com/ to example.com/subs/<subdomain/

RewriteCond $1 !^subs/
RewriteCond %{HTTP_HOST} !^www\.example\.com
RewriteCond %{HTTP_HOST} ^([^.]+)\.example\.com
RewriteRule (.*) /subs/%1/$1 [L]

Internally rewrite .example.com/ to example.com/<subdomain/

RewriteCond %{ENV:Rewrite-Done} !^Yes$
RewriteCond %{HTTP_HOST} !^www\.example\.com
RewriteCond %{HTTP_HOST} ^([^.]+)\.example\.com
RewriteRule (.*) /%1/$1 [E=Rewrite-Done:Yes,L]

In both cases, a mechanism is required (and present in the code) to prevent an ‘infinite’ rewriting loop.

If you use the first method, then you can easily externally redirect direct client requests for the subdomain-subdirectories back to the subdomain to avoid duplicate content:

Externally redirect client requests for example.com/subs// to .example.com/

RewriteCond %{THE_REQUEST} ^[A-Z]{3,9}\ /subs/
RewriteRule ^subs/([^/]+)/(.*)$ http://$1.example.com/$2 [R=301,L]

Here more complex email
The best way to do this is to setup each (or all) subdomain in the sites/{subdomain} directory of domain.com via your control panel. Some hosts will leave well enough alone (so the subdomain remains visible) but others actually force a redirect to the main domain’s subdirectory (forcing a change of URL). If you do this with mod_rewrite, you are forcing the change of URL.

# Rewrite <subdomain>.example.com/<path> to example.com/SITE/<subdomain>/<path>
#
# Skip rewrite if no hostname or if subdomain is www
# RewriteCond %{HTTP_HOST} .
# there must always be an {HTTP_HOST}
RewriteCond %{HTTP_HOST} !^www\. [NC]

# Extract (required) subdomain (%1), and first path element (%3), discard port number if present (%2)
RewriteCond %{HTTP_HOST}<>%{REQUEST_URI} ^([^.]+)\.domain\.com(:80)?<>/([^/]*) [NC]
# / is not used by Apache 2.x
# ([^/]*) means no subdirectories allowed

# Rewrite only when subdomain not equal to first path element (prevents mod_rewrite recursion)
RewriteCond %1<>%3 !^sites/(.*)<>\1$ [NC]
# Don't forget your sites "marker" subdirectory
# \1$ has no meaning!  All you don't want it sites/ in the URI

RewriteCond %{REQUEST_URI} !^/?sites/
# so you don't need the preceding RewriteCond statement

RewriteRule ^(.*) sites/%1/$1 [R=301,L]
# You might as well make this a 301 redirect
# finis!

    # Rewrite to /subdomain/path
    #RewriteRule ^(.*) /sites/%1/$1 [L]
    #RewriteRule ^(.*) /%1/$1 [L] #root directory
    #RewriteRule ^(.*) sites/%1/$1 [L]
    #RewriteRule ^/products/ index.php?id=$1&todo=

To check whether the folder exists is redundant – Apache will NOT even receive the request if the subdomain doesn’t exist so this problem can only occur with Dynamic Mass VirtualHosting. In that case, use a RewriteCond statement to check {PHYSICAL path to DocumentRoot}/sites/%1 -d (directory exists).