Ceci n'est pas une pipe

Today I write from my new workplace. I am on the third floor of a building in an unidentified area of ​​the city of Brescia. Like the salmon, I finally climbed back flow karst of my online existence and went back to basics. This is basically where I come from the city. There is still everything upside down, but we have what we need to work, to work well, the'll finish later. There is a beautiful sky here today in Brescia, I hope to keep the rest of the week. Well, now I come to my things. After all, they are now half of Brescia, I can not stay with our arms folded ... Only one thing, I took the next photo here on the web, it's not my stuff. See you!

I write here as a reminder for the next time this happens ... This morning I have placed a link a new FTP access to one of my Debian server, running ProFTPD always been a very well performing.

The colleague pointed me to serious problems of slow and repeated timeouts on FTP connection, a phenomenon that in over a year of production servers that had never shown: dozens of customers regularly access via FTP to the DocumentRoot of your VirtualHost enjoying full bandwidth availability and disk space.

After verifying that the problem only access to my FTP server and after we make sure that his connection had no problems on port 21, the mists of my poor memory has re-emerged as if by magic the question of reverse lookup! ProFTPD has to disable it completely solved the problem ... it was simply appended to the file / etc / proftpd / proftpd.conf the following two directives:

UseReverseDNS off
IdentLookups off

ProFTPD restart the problem is back into nothingness from which it originated

Here I succulentissimo a video posted yesterday by Luigi Rizzo, University of Pisa on Google Tech Talk. Really interesting, do not miss it!

Those who have the bad habit of installing web applications in the document root are often faced with an annoying problem: the inability to manage directories and subdirectories outside the application because of access restrictions imposed by the. Htaccess file.

The most typical example is that of the Drupal CMS. Suppose to have it installed and made fully accessible at URL:

http://www.miodominio.xx/

The. Htaccess Drupal will check everything that may or may not be accessible under the own document root, which in this case coincides exactly with the document root of the virtual hosts. In fact. Htaccess file is located in the root file system dedicated to this application:

http://www.miodominio.xx/.htaccess

In this way, if we decide to create any new directories, this will suffer the same restrictions written into the file. Htaccess when installing Drupal, such as the inability to navigate freely among its files and subdirectories that it contains:

http://www.miodominio.xx/test/

This directory is not accessible in this way, but only by invoking the name of the file in it we want to access, for example:

http://www.miodominio.xx/test/pippo.html
http://www.miodominio.xx/test/imago.jpg

If you do not specify a file it is the only tried and shown index.php file:

http://www.miodominio.xx/test/index.php

If the index.php file does not exist, it does not show the contents of the directory - as many would expect - but rather is generated bell'errore 404 (File Not Found).

To overcome this problem is sufficient to release the file. Htacces, adding instructions that make the directory / test / immune to these rules, immediately after initializing the RewriteEngine:

<IfModule mod_rewrite.c>
RewriteEngine on
#
# ECCO LE DUE RIGHE DI ISTRUZIONI:
RewriteCond %{REQUEST_URI} "/test/"
RewriteRule (.*) $1 [L]
#

Seeing is believing.

A straight fast if you asked me a way to remedy the SSH timeout. I state that this is a situation increasingly common, due to the default configuration of the new router distributed by Telecom for Alice ADSL. The problem can be solved by passing the parameter to the ssh command:

-o ServerAliveInterval=10

The parameter sends a message to noop to the server every n seconds (in this case: 10) informs the router that the connection is actually working, even in the absence of any type of activity. Since it is not convenient type it every time, you can update your file. Bashrc with an alias that incorporates the option in the basic command:

alias ssh="ssh -o ServerAliveInterval=10"

This is what