To see which process is keeping the file open:

Now you know the process, you can kill or restart it and the file will be released and deleted.

With this field type you can search with a string to get an exact match, instead of a contains match that the “text_general” field type will give you. However another difference is that the “text_general” field type is case insensitive by default and “string” is case sensitive.

To perform an case insensitive exact match search, you’ll have to add a custom field type in your Solr schema.xml, I called it “string_ci” (string case insensitive).

However if you enable them with the solr.StopFilterFactory the stop words still are not removed. This is caused by the “|” pipe characters after each word. Solr wants every word on a new line without anything else. Also replacement of | to # doesn’t work. This problem can be hard to discover if you expect that information provided by the Solr website should just work.

So to still contain the nice comments, it’s best to put them above each word. Besides that I replaced all | characters with #.

Stop words should be working perfectly now! If you want to use multiple stop word files check out http://pietervogelaar.nl/solr-multiple-stop-word-files.

To accomplish this, you’ll have to do some simple steps. I assume you already have a Git clone on your computer, go to the root directory of your clone and make sure you are in the master branch.

git branch -a

The branch with the “*” character before the name is the active one. Create a new branch “1.x” based on the master:

git checkout -b 1.x

A local branch 1.x should be created, you can check with “git branch -a”. The next command pushes the branch to the remote repository origin and tracks it.

git push -u origin 1.x

The branch exists now locally and in the remote Git repository. The active local branch is 1.x, check with “git branch -a”. If you want to work on the master branch again execute:

git checkout master

Install Webalizer

apt-get install webalizer

First change the default webalizer config.

nano /etc/webalizer/webalizer.conf

Incremental processing allows multiple partial log files to be used instead of one huge one. And OpenPanel creates multiple files by default, so lets set “incremental” to yes.

#Incremental     no
Incremental     yes

OpenPanel created apache log files per virtual host, so we don’t have to do that by ourselves. The access log files are located at “/var/log/apache2/openpanel/logs”.

To generate stats from an apache access log file, you’ll have to execute the following command:

/usr/bin/webalizer -c /etc/webalizer/webalizer.conf -n www.example.com -s www.example.com -r www.example.com -q -T -o /var/www/webalizer/www.example.com /var/log/apache2/openpanel/logs/www.example.com.log

I created a shell script to automatically create stats for all virtual hosts. Put it for example at “/opt/webstats.sh”

Create a cronjob for it with:

crontab -e

And add the following file to generate stats every 5 minutes:

*/5 * * * * /opt/webstats.sh

If you want to view the stats in your browser go to “http://myserveripaddress/webalizer/www.example.com”. But you probably also want access with “http://www.example.com/webalizer”. To make this happen, extend your virtual host file with:

nano /etc/apache2/openpanel.d/www.example.com.inc/extended.conf

And add:

Alias /webalizer /var/www/webalizer/www.example.com

Restart the Apache web server

service apache2 restart

And you’re done! Everything should be working smoothly now.

Password protection

Optionally, you can also add password protection to the Webalizer directory. This way your stats will not be publicly available for everyone. Add the following commands to add the protection.

nano /var/www/webalizer/.htaccess

And add:

AuthGroupFile /dev/null
AuthName "Password Protected Area"
AuthType Basic
AuthUserFile /var/www/webalizer/.htpasswd
require valid-user

Create .htpasswd:

touch /var/www/webalizer/.htpasswd

And add a user (for example “admin”), you’ll be prompted to define a password.

htpasswd /var/www/webalizer/.htpasswd admin

Restart Apache web server

service apache2 restart

All your virtual host stats are password protected now with the user/pass defined above.

Close Netbeans. Remove the cache folder:

rm -rf "/home/YOURNAME/.netbeans/var/cache"

Start Netbeans 7 and everything should be working fine again!

Problems:
- If you click on the icon again, it will try to start a new instance of Netbeans. Netbeans will see that it’s already opened, so it will not start another instance, but this way it’s still dirty and slow.
- Unity will forget the link on reboot, so the icon disappears.

To solve these problems, download http://plugins.netbeans.org/plugin/40321/unity-launcher first.

Open Netbeans and go to Tools -> Plugins -> Downloads -> Add plugin. Select the downloaded Unity launcher plugin there and install it. Close Netbeans after installation.

As of Netbeans 7.1 the file described below is automatically created with also the correct permissions. For older versions than Netbeans 7.1 you’ll must proceed with the steps below.

Open a terminal and execute the following:

nano /home/YOURNAME/.local/share/applications/netbeans.desktop

And add the following with some minor changes of your own:

[Desktop Entry]
Name=Netbeans
Comment=Netbeans IDE
Exec=/home/YOURNAME/netbeans-7.0/bin/netbeans
Icon=/home/YOURNAME/netbeans-7.0/nb/netbeans.png
Terminal=false
Type=Application
StartupNotify=true
StartupWMClass=netbeans

Give your user execution rights:

chmod u+x /home/YOURNAME/.local/share/applications/netbeans.desktop

Now reboot your system and everything should work correctly!

sudo dpkg -i downloaded_package.deb

You will probably get errors about missing packages (dependencies) now. Execute:

sudo apt-get -f install

You’re done! The debian package is now successfully installed with all its dependencies!

Set the grid attribute:

If the tab is clicked the following code must be executed to load the Grid data: