Auctex mode in Emacs on Ubuntu(Jaunty)


sudo apt-get install auctex, preview-latex-style

#Once installed add the below mentioned part in your ".emacs" file.

;; Math mode for LaTex (add-hook 'LaTeX-mode-hook 'LaTeX-math-mode)

;;mouse scrolling (mouse-wheel-mode t)

;; spellcheck in LaTex mode (add-hook `latex-mode-hook `flyspell-mode) (add-hook `tex-mode-hook `flyspell-mode) (add-hook `bibtex-mode-hook `flyspell-mode)

;; Show line-number and column-number in the mode line (line-number-mode 1) (column-number-mode 1)

;; highlight current line (global-hl-line-mode 1)

Restart Emacs and you have Auctex enabled. 😀

Setting Up Local Ubuntu(Jaunty) Repository via Apt-Mirror.

The article mentions the method to deploy APT-MIRROR so that you can use a local repository in your intranet insted going to internet again.
I will use the local repository IP to 192.100.100.40

Packages required:–
1.Apt-Mirror
2.Apache Webserver (to distribute to whole intranet)
Steps :—

1.Setting up the apt-mirror

$sudo apt-get install apt-mirror
$sudo nano  /etc/apt/apt-mirror <---- (the configuration file of apt-cache)

---------------------------XXXXXXXXXXXXXXXXX--------------------
############# config ##################
#
#set base_path    /var/spool/apt-mirror
# if you change the base path you must create the directories below with
write privileges
#
# set mirror_path  $base_path/mirror
# set skel_path    $base_path/skel
# set var_path     $base_path/var
# set cleanscript $var_path/clean.sh
set defaultarch  
set nthreads     20
set _tilde 0
#
############# end config ##############
deb-i386 http://archive.ubuntu.com/ubuntu jaunty main restricted
universe multiverse
deb-i386 http://archive.ubuntu.com/ubuntu jaunty-updates main restricted
universe multiverse
deb-i386 http://archive.ubuntu.com/ubuntu jaunty-backports main
restricted universe multiverse
deb-i386 http://archive.ubuntu.com/ubuntu jaunty-security main
restricted universe multiverse
deb-i386 http://archive.ubuntu.com/ubuntu jaunty-proposed main
restricted universe multiverse
clean http://archive.ubuntu.com/ubuntu
-------------------------XXXXXXXXXXXXX----------------------------------------

I am creating local repo for Jaunty you can replace it with karmic or hardy incase you want a repo of that Disros. In above configuration file what i have done is my source file for
downloading whole package is /var/spool/apt-mirror. I wanted the repository for the 32 bit system so i mentioned deb-i386. You can replace/add deb-amd64 if you want only 32 bit repo or incase
you want repo for both architecture.

2.Dumping the packages in local repository.

$sudo apt-mirror

You will see something like this on your screen/terminal
-------------------------XXXXXXXXX---------------------------------------------
t143@t143-desktop:/var/log$ sudo apt-mirror
Downloading 90 index files using 20 threads...
Begin time: Thu Feb 11 16:32:14 2010
[20]... [19]... [18]... [17]... [16]... [15]... [14]... [13]... [12]...
[11]... [10]... [9]... [8]... [7]... [6]... [5]... [4]... [3]... [2]...
[1]... [0]...
End time: Thu Feb 11 16:32:18 2010
Proceed indexes: [PPPPPP]
28.0 GiB will be downloaded into archive.
Downloading 29319 archive files using 20 threads...
Begin time: Thu Feb 11 16:32:26 2010
[20]...
--------------------------XXXXXXXXXX--------------------------------

This will take some time as 30 GB downloading takes sometime

3.Clean Up The Local Repo

t143@t143-desktop:$ sudo /bin/bash /var/spool/apt-mirror/var/clean.sh
Removing 157 unnecessary files [13316096 bytes]...
[0%]................done.
Removing 18 unnecessary directories...
[0%]..................done.

3.Mirroring it for the intranet
In case you don not have apache installed

$sudo apt-get install apache2



4.Create A Daily Cron Job


t143@t143-desktop:/var/log$ /etc/cron.d/apt-mirror

#
# Regular cron jobs for the apt-mirror package
#
0 4     * * *   apt-mirror      /usr/bin/apt-mirror >
/var/spool/apt-mirror/var/cron.log



This will make apt-mirror run at 4.00  each day, and it will log to

/var/spool/apt-mirror/var/cron.log.


5. Local Mirrors Accessible Over HTTP


Once apache installed and running


$cd /var/www
$sudo ln -s /var/spool/apt-mirror ubuntu
Now my repo address over intranet will become :--
deb http://192.100.100.40/ubuntu jaunty main restricted universe
multiverse
deb http://192.100.100.40/ubuntu jaunty-updates main restricted universe
multiverse
deb http://192.100.100.40/ubuntu jaunty-backports main restricted
universe multiverse
deb http://192.100.100.40/ubuntu jaunty-security main restricted
universe multiverse
deb http://192.100.100.40/ubuntu jaunty-proposed main restricted
universe multiverse
6.Testing our local repository
lets add this to one of the host computer on intranet
$sudo nano /etc/apt/sources.list
Lets add our local repo address inside it

deb http://192.100.100.40/ubuntu jaunty main restricted universe
multiverse
deb http://192.100.100.40/ubuntu jaunty-updates main restricted universe
multiverse
deb http://192.100.100.40/ubuntu jaunty-backports main restricted
universe multiverse
deb http://192.100.100.40/ubuntu jaunty-security main restricted
universe multiverse
deb http://192.100.100.40/ubuntu jaunty-proposed main restricted
universe multiverse




$sudo apt-get update

here we go we have all the packages coming from our local repository.

cheers!!!

Installing/Compiling Nagios03 on rhel5

Okey i been planning to do this long back.on rhel5 box here is a simple
guide i have made which lets you compile nagio3 from source and install
in RHEL5 box.
Make sure you have these packages installed:–
1.Apache
2. GCC compiler
3.GD development libraries
You can use “yum” to install these packages by running the following
commands (as root):
yum install httpd gcc glibc glibc-common gd gd-devel
Create a new nagios user account and give it a password.
/usr/sbin/useradd -m nagios
passwd nagios
Create a new nagcmd group for allowing external commands to be submitted
through the web interface.
Add both the nagios user and the apache user to the group.
/usr/sbin/groupadd nagcmd
/usr/sbin/usermod -a -G nagcmd nagios
/usr/sbin/usermod -a -G nagcmd apache
2) Download Nagios and the Plugins Create a directory for storing the downloads.
mkdir ~/downloads
cd ~/downloads
Download the source code tarballs of both Nagios and the Nagios plugins (visit http://www.nagios.org/download/ for links to the latest versions).
wget http://sourceforge.net/projects/nagios/files/nagios-3.x/nagios-3.2.1/nagios-3.2.1.tar.gz/download
wget http://sourceforge.net/projects/nagiosplug/files/nagiosplug/1.4.14/nagios-plugins-1.4.14.tar.gz/download
3) Compile and Install Nagios Extract the Nagios source code tarball.
cd ~/downloads tar xzf nagios-3.2.1tar.gz
cd nagios-3.2.1
Run the Nagios configure script, passing the name of the group you created earlier like so:
./configure –with-command-group=nagcmd

Compile the Nagios source code. make all Install binaries, init script, sample config files and set permissions on the external command directory.
make install
make install-init
make install-config
make install-commandmode
Don’t start Nagios yet – there’s still more that needs to be done…
4) Customize Configuration Sample configuration files have now been installed in the /usr/local/nagios/etc directory. These sample files should work fine for getting started with Nagios. You’ll need to make just one change before you proceed…
Edit the /usr/local/nagios/etc/objects/contacts.cfg config file with your favorite editor and change the email address associated with the nagiosadmin contact definition to the address you’d like to use for receiving alerts.
vi /usr/local/nagios/etc/objects/contacts.cfg
5) Configure the Web Interface Install the Nagios web config file in the Apache conf.d directory. make install-webconf
Create a nagiosadmin account for logging into the Nagios web interface. Remember the password you assign to this account – you’ll need it later.
htpasswd -c /usr/local/nagios/etc/htpasswd
users nagiosadmin Restart Apache to make the new settings take effect.
service httpd restart
Implementing Digest Authentication
The implementation of Digest Authentication is simple. You will have to create the new type of password file using the ‘htdigest’ tool, then modify the Apache configuration for nagios (typically /etc/httpd/conf.d/nagios.conf).
Create a new passwords file using the ‘htdigest’ tool. The difference that you will notice if you are familiar with ‘htpasswd’
tools is the requirement to supply a ‘realm’ argument. Where ‘realm’ in this case refers to the value of the ‘AuthName’ directive in the Apache configuration.
htdigest -c /usr/local/nagios/etc/.digest_pw “Nagios
Access” nagiosadmin Next, edit the Apache configuration file for Nagios(typically /etc/httpd/conf.d/nagios.conf) using the following example.
## BEGIN APACHE CONFIG SNIPPET – NAGIOS.CONF ScriptAlias /nagios/cgi-bin
“/usr/local/nagios/sbin”
Options ExecCGI AllowOverride None Order allow,deny Allow from all
AuthType Digest AuthName “Nagios Access” AuthUserFile
/usr/local/nagios/etc/.digest_pw Require valid-user Alias /nagios
“/usr/local/nagios/share” Options None AllowOverride None Order
allow,deny Allow from all AuthType Digest AuthName “Nagios Access”
AuthUserFile /usr/local/nagios/etc/.digest_pw Require valid-user
## END APACHE CONFIG SNIPPETS
Then, restart the Apache service so the new settings can take effect.
/etc/init.d/httpd restart
6) Compile and Install the Nagios Plugins Extract the Nagios plugins source code tarball.
cd ~/downloads tar xzf nagios-plugins-1.4.14.tar.gz
cd nagios-plugins-1.4.14
Compile and install the plugins.
./configure –with-nagios-user=nagios –with-nagios-group=nagios
make
make install
7) Start Nagios Add Nagios to the list of system services and have it automatically start when the system boots.
chkconfig –add nagios
chkconfig nagios on
Verify the sample Nagios configuration files.
/usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg
If there are no errors, start Nagios.
service nagios start
9) Login to the Web Interface You should now be able to access the  Nagios web interface at the URL below. You’ll be prompted for the username (nagiosadmin) and password you specified earlier.
http://localhost/nagios/
Click on the “Service Detail” navbar link to see details of what’s being monitored on your local machine.
It will take a few minutes for Nagios to check all the services  associated with your machine, as the checks are spread out over time.
refernce :– nagios manual