1. Install the necessary build tools

You may find that you need some additional development libraries depending on what is already installed on your system.
sudo apt-get install build-essential libglut3-dev libxi-dev libxmu-dev

2. Download the CUDA driver, Toolkit, and SDK from developer.nvidia.com
3. Install the CUDA driver

The nVidia driver cannot be installed while X is running, so you will need to stop gdm and install the driver in a virtual console by pressing ctrl+alt+F1. If you have already installed the Ubuntu restricted driver for your nVidia graphics card like I did, you will probably run into some trouble installing the CUDA driver. I solved my problems by following the nVidia driver manual installation guide here. The normal process if there are no conflicting drivers already installed are as follows.
chmod +x NVIDIA-Linux-x86-xxx-pkg1.run
sudo /etc/init.d/gdm stop
sudo ./NVIDIA-Linux-x86-xxx-pkg1.run
sudo /etc/init.d/gdm start

4. Install the CUDA toolkit

chmod +x NVIDIA_CUDA_Toolkit_2.1_ubuntu8.04_x86.run
sudo ./NVIDIA_CUDA_Toolkit_2.1_ubuntu8.06_x86.run

5. Modify Environment Variables

The simplest way to do this is to edit your ~/.bashrc file. Changes take effect when you start a new terminal session.
PATH=$PATH:/usr/local/cuda/bin
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/cuda/lib
export PATH
export LD_LIBRARY_PATH

6. Install the CUDA SDK

chmod +x ./NVIDIA_CUDA_SDK_xxx_linux.run
./NVIDIA_CUDA_SDK_xxx_linux.run

7. Compile and Run the example programs

cd ~/NVIDIA_CUDA_SDK
make

Now execute any of the example programs in ~/NVIDIA_CUDA_SDK/bin/linux/release/

Check out http://lifeofaprogrammergeek.blogspot.com/2008/05/cuda-development-in-ubuntu.html for similar details and how to copy the template project and start coding your own CUDA program.

This week Linux Journal magazine has been running a contest and the prize is a one year free subscription to the digital edition of their magazine.

All you have to do to enter is head over to Linux Journal and watch this week’s series of Tech Tip Videos (the ones marked “This is Tech Tip Video Contest Week (March 9 – 13) at LinuxJournal.com!”). Throughout those videos they sprinkled secret letters. You just have to find the secret letters over the course of the week and unscramble them to produce a linux related phrase. Once you have unscrambled the letters, head over to the contest submission form and submit it to win a free subscription.

Hurry! The contest ends at 11:59:59PM EDT, Friday, March 13 2009. That’s tonight!

Here’s the official contest announcement from Monday.

On the remote host (machine to be monitored)

1. Become root. This just makes it easier so you don’t have to keep typing sudo.
# sudo -s

2. Create nagios user and set password
$ /usr/sbin/useradd nagios
$ passwd nagios

3. Install the OpenSSL development libraries required to compile the NRPE plugin
$ apt-get install libssl-dev openssl

4. Download source tarball of Nagios plugins (http://www.nagios.org/download)
$ wget <nagios-plugins, latest stable version>

5. Extract the tarball
$ tar xzf <nagios-plugins...>.tar.gz
$ cd <nagios-plugins...>

5a. (optional) Install additional libraries required for any plugins that you will need. See the REQUIREMENTS document included with nagios plugins source code for any dependencies necessary for specific plugins.

6. Compile and install the plugins
$ ./configure
$ make
$ make install

7. Fix the permissions on the plugin directory and the plugins
$ chown nagios:nagios /usr/local/nagios
$ chown -R nagios:nagios /usr/local/nagios/libexec

8. Install xinetd
$ apt-get install xinetd

9. Install the NRPE daemon, download the source tarball for NRPE from http://www.nagios.org/download
$ wget <nrpe, latest stable version>
$ tar xzf <nrpe...>.tar.gz
$ cd <nrpe...>
$ ./configure
$ make all

$ make install-plugin
$ make install-daemon
$ make install-daemon-config
$ make install-xinetd

10. Edit /etc/xinetd.d/nrpe and add the IP address of the monitoring server to the only_from directive. This directive can contain multiple IP addresses provided in a space separated list. This example will allow access from the Nagios monitoring server as well as the localhost.
$ vi /etc/xinetd.d/nrpe

. . .

only_from =xxx.xxx.xxx.xxx 127.0.0.1

11. Edit /etc/services to add the NRPE port definition
$ vi /etc/services

. . .

nrpe 5666/tcp # NRPE

12. Restart xinetd
$ /etc/init.d/xinetd restart

13. Test the NRPE daemon locally

First, use netstat to make sure that it is running under xinetd
$ netstat -at | grep nrpe
should produce this output:
tcp 0 0 *:nrpe *:* LISTEN

Now give it a test using the Nagios check_nrpe plugin:
$ /usr/local/nagios/libexec/check_nrpe -H localhost
You should see this output (with the appropriate version number of course)
NRPE v2.12

14. At this point you should be able to access the Nagios NRPE daemon on this host from the monitoring server to execute plugins locally. Make sure to modify your firewall rules to allow access on port 5666 to the NRPE daemon. The commands that are to be executed by the NRPE plugin can be customized in /usr/local/nagios/etc/nrpe.cfg.

On the monitoring host (machine running nagios)

1. Become root
$ sudo -s

2. Download and install the check_nrpe plugin (http://www.nagios.org/download)
$ wget <nrpe, latest stable version>
$ tar xzf <nrpe...>.tar.gz
$ cd <nrpe...>
$ ./configure
$ make all
$ make install-plugin

3. Test communication with remote NRPE daemon
$ /usr/local/nagios/libexec/check_nrpe -H <hostname>
Your output should look like this if everything is successful (with the proper version number again).
NRPE v2.12

4. Create the NRPE command definition wherever in your configuration files you have commands defined.
$ vi /usr/local/nagios/etc/objects/commands.cfg

. . .

define command{
    command_name check_nrpe
    command_line $USER1$/check_nrpe -H $HOSTADDRESS$ -c $ARG1$
}

5. Now you can create host and service definitions for the remote host and begin monitoring local services through the NRPE plugin and daemon.
SAMPLE:
define service{
    use generic-service
    host_name remotehost
    service_description Current Users
    check_command check_nrpe!check_users
}
; check_nrpe tells the remote nrpe daemon to execute
; the check_users command as defined in nrpe.cfg

6. Verify your configuration and restart the Nagios daemon to begin monitoring the remote host.
Verify your nagios configuration:
$ /usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg
If everything checks out, restart the Nagios daemon:
$ /etc/init.d/nagios restart

The way to direct HTTP traffic to HTTPS is with the mod_rewrite URL Rewriting Engine module in Apache. Here is the process that I used earlier today on an Ubuntu 8.04 Server with Apache2.

First enable the rewrite module using the a2enmod utility:

$ sudo a2enmod rewrite

Next edit /etc/apache2/sites-available/default to redirect the port 80 virtual host to the port 443 virtual host.

$ sudo vi /etc/apache2/sites-available/default

<VirtualHost *:80>
RewriteEngine on
RewriteCond %{SERVER_PORT} ^80$
RewriteRule ^(.*)$ https://%{SERVER_NAME}$1 [R,L]
. . .
</VirtualHost>

RewriteEngine on enables mod_rewrite on this virtual host. RewriteCond %{SERVER_PORT} ^80$ matches all requests on port 80, then RewriteRule ^(.*)$ https://%{SERVER_NAME}$1 [R,L] rewrites the request making it an https:// request. Now all requests coming in on port 80 (HTTPS) will be redirected to port 443 (HTTPS).

Now save em>/etc/apache2/sites-available/default and reload the Apache configuration to make the rewrite active.

$ sudo /etc/init.d/apache2 reload

For more information regarding Apache mod_rewrite or more details related to the rewrite rules structure and regular expressions see the documentation.