Nessus messages at the securepoint message boards - quite a few on starting nessusd at boot.

After all that faffing with GRUB and boot disks, I have, as usual, found what I need in a nice, straightforward Linux command, mkbootdisk.
The snytax is
mkbootdisk --device /dev/fd0 2.4.2-3
if you use kernel 2.4.2-3, for example.
To find which kernel you run, you can just check with a good old
uname -a

OpenLDAP.org have some lovely Open Source LDAP tools.

This article usefully describes the init.d (or xinit.d) service scripts that you might use to automate the start of a daemon or service.

.....and here's some more on that VMWare RH9 issue. Looks like static IP fixes things. I can live with that.

Having troubles with Red Hat 9.0 VM running in VMWare Workstaion 4.0 on an XP host system. Basically, the network doesn't fire up as Red Hat seems to think that the interface is not connected.
There's a bloke here who had the same problem, but unfortunately he doesn't describe his fix.

Red Hat have launched an Open Source Best Practices site.

howto create a boot disk in red hat 7.2.
I also found this and this on making a GRUB boot disk.
The problem I have is that when you restore a red hat 7.2 server from a Ghost clone image, the MBR is knackered, so GRUB doesn't work. The best description of creating the boot floppy is in the offical docs here, but this talks about using it to restore the MBR.

.......and also notes on installing red hat 7 in a VMWare workstation host, including installing the VMware tools.

getting started with heartbeat, for high availability Linux.
holy crap.

I very much doubt that anyone other than me reads this blog regularly; it's just a fragmented diary of my journey through the world of open source and, more often than not, Linux.
My efforts in this area are not consistent, and depend a lot on how much free time I can find to play with stuff, which recently hasn't been much.

Anyway, things might pick up a little now as I have actually got to do a few things in a production environment now, which are:
- Configure network backups for two Red Hat servers.
- Try and build a second Apache Tomcat server running on Linux, to match an existing server.
- Investigate and understand a "heartbeat" technology (clustering of a sort) for Apache servers on Linux.

I'm excited to be using Linux for real, but a bit scared....... :)

So, the command line to fire up the firewall configuration utility in Red Hat is
redhat-config-securitylevel

Found out today that /proc/cpuinfo gives you (you guessed it) the cpu info for the server. Hence:
cat /proc/cpuinfo
will tell you about the processors on a machine.

Also, I don't know how I would have got on today if I hadn't been shown this ssh client, which natively supports file transfer via a GUI. Also, it's free for non-commercial use. :)