]> http://www.sharons.org.uk/taste My thoughts on linux and other random thoughts. en-us Sharon 2007-06-03T13:27:39+01:00 http://www.sharons.org.uk/taste/archives/2007/06/index.html#e2007-06-03T13_27_32.txt 2007-06-03T13:27:32+01:00 Sharon
it turns out that I needed to alter usr/share/config/kdm/kdmrc, and the line that has to be changed is Theme=/usr/share/apps/kdm/themes/RHEL and I changed it to 'circles' and then rebooted. And I was able to log out properly which was another of my problems. When the login screen reappeared after my reboot there was a big flower and two boxes requesting my login details, it was working! Once in I went back to the above mentioned file and changed the theme to 'Bluecurve' and logged out, to be met with two login boxes in a more official looking blue background, which is what I prefer. Another problem solved :)]]> http://www.sharons.org.uk/taste/archives/2007/03/index.html#e2007-03-17T22_19_38.txt 2007-03-17T22:19:38+01:00 Sharon ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
# DO NOT EDIT THIS FILE - edit the master and reinstall.
# (/tmp/croninit installed on Mon Feb 23 12:02:14 2004)
# (Cron version -- $Id: crontab.c,v 2.13 1994/01/17 03:20:37 vixie Exp $)
# Min Hour DoM Month DoW Command
MAILTO="boztu"
LANG="en_GB"
0 0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23 * * * /home/boztu/programs/eggdrop/iceni.botchk
#0 * * * * /home/boztu/foldingathome/folding status 1 >/opt/logwatch/folding.txt
#* */12 * * * /home/boztu/chk_pending.sh >/opt/logwatch/pending.txt
#@reboot /home/boztu/reboot.sh
#0 7 * * * /home/boztu/backup.sh 0
#0 */6 * * * /home/boztu/backup.sh 1
30 4 * * */3 /usr/bin/sa-learn --ham --mbox /home/boztu/Mail/inbox-mbox
30 4 * * */3 /usr/bin/sa-learn --spam --mbox /home/boztu/Mail/SPAM
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
from which you can see that I run an eggdrop bot which is checked every hour to see if its running, and if not to start it up.
And that every 3 days I run spamassassin learn on my spam mailbox.]]> http://www.sharons.org.uk/taste/archives/2007/03/index.html#e2007-03-14T20_12_35.txt 2007-03-14T20:12:35+01:00 Sharon
Our March meeting was very pleasant with good food reasonably priced and good beer also at a reasonable price. The conversation ranged over favourite distro, and favourite editor, to the Reiser murder case and the quality of the beer! And as its a Shepherd Neame pub the beer quality was high!

A quick straw poll indicated that we've now found our social meeting 'home' and this is where we'll be meeting for the foreseeable future.]]> http://www.sharons.org.uk/taste/archives/2007/01/index.html#e2007-01-11T13_40_37.txt 2007-01-11T13:40:37+01:00 Sharon
On the fourth Friday of each month we're holding a social meeting in Canterbury at the 'Old Bev', Canterbury [come out of the west station as if you've just arrived from Maidstone, turn left, go 100m, on the left is a footpath signposted "university" and "whitstable, follow that, go under the bridge, keep following the path straight, you then come out at a small monument/green and on your left is the Old Bev pub]. Same time different place.]]> http://www.sharons.org.uk/taste/archives/2006/11/index.html#e2006-11-08T19_06_29.txt 2006-11-08T19:06:29+01:00 Sharon http://www.sharons.org.uk/taste/archives/2006/10/index.html#e2006-10-04T19_53_31.txt 2006-10-04T19:53:31+01:00 Sharon
0 */6 * * * /usr/bin/rsnapshot hourly
00 23 * * * /usr/bin/rsnapshot daily
40 23 * * 0 /usr/bin/rsnapshot weekly
20 23 1 * * /usr/bin/rsnapshot monthly
55 0,6,12,18 * * * DATE=`date` UPTIME=`uptime` ; echo "$DATE, $UPTIME" >>/opt/logwatch/rsnapshot.txt ; /usr/bin/rsnapshot du >>/opt/logwatch/rsnapshot.txt

The first line fires it off every six hours to do a full backup, the second line changes the earliest hourly snapshot to be the daily snapshot. The third line changes the earliest daily snapshot to be a weekly snapshot only if it occurs on a Sunday. The fourth line makes the daily snapshot be the monthly snapshot but only if it is the first of the month. And the fifth line writes the date and machine uptime to a separate file 55 minutes after the six hourly backups, and also tells you how much disc space all the backups take.

It all works, but takes longer to explain. Why not try my crontab incantation and try out rsnapshot for yourself?]]> http://www.sharons.org.uk/taste/archives/2006/09/index.html#e2006-09-16T16_10_13.txt 2006-09-16T16:10:13+01:00 Sharon
sa-learn --no-sync --spam --mbox /home/boztu/Mail/SPAM

sa-learn --no-sync --ham --mbox /home/boztu/Mail/inbox-mbox

sa-learn --sync

sa-learn --dump magic

The first obviously learns the spam, the second the 'ham' or good emails, the third rebuilds the SpamAssassin database, and the fourth shows you what its learnt.

All good stuff.]]> http://www.sharons.org.uk/taste/archives/2006/08/index.html#e2006-08-24T20_47_31.txt 2006-08-24T20:47:31+01:00 Sharon
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cfgmaker --global 'WorkDir: /var/www/mrtg' --global 'Options[_]: bits,growright' --output /etc/mrtg/mrtg.cfg public@localhost
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

One less hassle now with the problem solved. :)]]> http://www.sharons.org.uk/taste/archives/2006/08/index.html#e2006-08-18T14_14_02.txt 2006-08-18T14:14:02+01:00 Sharon
One of its members [Simon Morris, aka 'mozrat'] provided me with the following code, which is saved as 'backup.sh' and obviously executable and saved in your 'home' folder;-
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
#!/bin/sh
#
# backup.sh - Backup control script
# written by Simon Morris [aka mozrat] 12-08-2006.
# Usage: backup.sh LEVEL
#
# where LEVEL = 0, 1
#

# Variables
EMAILTO="boztu@localhost"
DESTFILE="/mnt/winj/backup/backup.`date +%Y%m%d-%H%M`.`date +%a`.tar.bz2"
BACKUPFILES="/etc /home/boztu /opt/logwatch /var/www"
BACKUPDIR="${HOME}/backup"
LEVEL="${1}"
###############################################
##### DO NOT CHANGE BENEATH THIS LINE##########
###############################################
# Load backup functions
cd ${BACKUPDIR}
. backup-functions

# Do some pre-flight work
pre_flight

# Do the backup
tar_backup

# Test the backup for errors
tar_verify

# Email the backup report
mail_report

# Done
exit
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The variables are self-evident and can be tweaked to your needs. However, don't tweak it whilst your running a backup as it finishes one backup and then immediately starts one using your new code.

And then there is the following code, which is saved in the 'backup' folder and called 'backup functions';-
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
# This is not a shell script; it provides functions for the backup.sh script
# that sources it.

# Variables
L0DATESTAMP="${BACKUPDIR}/.level0_datestamp"
NOW=`date`

# Some pre-flight checks
pre_flight ()
{
dpkg -l > /root/backup/dpkg/dpkg.`date +%Y%m%d`.`date +%a`.txt
mysqldump --all-databases > /root/backup/mysql/mysql.`date +%Y%m%d`.`date +%a`.txt
for list in `list_lists -b`
do
config_list -o /root/backup/mailman/$list.`date +%Y%m%d`.`date +%a`.txt $list
list_members $list > /root/backup/mailman/$list.`date +%Y%m%d`.`date +%a`
-members.txt
done

}

# tar_backup function: does the archiving
tar_backup ()
{
echo "Level-${LEVEL} Backup ${NOW}"
if [ "${LEVEL}" = "0" ]; then
# make Level-0 datestamp
echo ${NOW} > ${L0DATESTAMP}
# Level-0 backup
tar --create --verbose \
--file ${DESTFILE} \
--blocking-factor 126 \
--label "Level-${LEVEL} Backup ${NOW}" \
--bzip2 \
${BACKUPFILES}
elif [ "${LEVEL}" = "1" ]; then
# get last Level-0 datestamp
LAST=`cat ${L0DATESTAMP}`
# Level-1 backup
tar --create --verbose \
--file ${DESTFILE} \
--blocking-factor 126 \
--after-date "${LAST}" \
--bzip2 \
--label "Level-${LEVEL} Backup from ${LAST} to ${NOW}" \
${BACKUPFILES}
else
# Backup level error
echo "Error: Level-${LEVEL} unknown"
exit
fi
echo "Level-${LEVEL} Backup END"
}

# tar_verify function: test the archive for errors
tar_verify ()
{
echo "Level-${LEVEL} Backup Verify ${NOW}"
# Backup verify test
tar --list --verbose \
--file ${DESTFILE} \
--blocking-factor 126
echo "Level-${LEVEL} Backup Verify END"
}

# mail_report function: sends backup report
mail_report ()
{
# Email backup report
mail -s "Level-${LEVEL} Backup" "${EMAILTO}" << EOF

###########################################################
Level-${LEVEL} Backup
###########################################################

Host: ${HOSTNAME}
Files: ${BACKUPFILES}

Destination: ${DESTFILE}

###########################################################
Started: ${NOW}
Completed: `date`
###########################################################

`cat /tmp/cpfile.txt`

EOF
}
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Then just set up crontab to call it whenever you want and it will do whatever you have called for in the variables in 'backup.sh'. Simple and works like a dream :)]]> http://www.sharons.org.uk/taste/archives/2006/07/index.html#e2006-07-30T14_20_28.txt 2006-07-30T14:20:28+01:00 Sharon
http://localhost/mywiki/FrontPage]]>