How to confirm hard drive ufsid before upgrade?

Hello. I recently upgraded 7 remote servers from FreeBSD 7.2 to 8.0. During the process, 3 servers had hard drive ufsid issues. Basically during the reboot between 7.2 to 8.0, the drive ids 'changed'. I'm using ufsids in fstab. All servers have two SCSI drives, but have all been set-up by

Re: Dual core CPU's, but only 2 CPU's in-use?

On Sun, 24 Feb 2008 15:59:49 +0100 Kris Kennaway [EMAIL PROTECTED] wrote: Tigger wrote: On Sun, 24 Feb 2008 12:46:23 +0100 Dominic Fandrey [EMAIL PROTECTED] wrote: Tigger wrote: Hello. I have a Xeon system with 2 CPU's installed (dual-cores). Under FreeBSD 6.2, a systat reported 4

Re: Dual core CPU's, but only 2 CPU's in-use?

On Mon, 25 Feb 2008 11:30:13 +0100 Kris Kennaway [EMAIL PROTECTED] wrote: Tigger wrote: On Sun, 24 Feb 2008 15:59:49 +0100 Kris Kennaway [EMAIL PROTECTED] wrote: Tigger wrote: On Sun, 24 Feb 2008 12:46:23 +0100 Dominic Fandrey [EMAIL PROTECTED] wrote: Tigger wrote: Hello. I

Dual core CPU's, but only 2 CPU's in-use?

Hello. I have a Xeon system with 2 CPU's installed (dual-cores). Under FreeBSD 6.2, a systat reported 4 CPUs in use and so did dmesg. Under FreeBSD 6.3, dmesg is reporting the 4 CPUs, but systat is only reporting 2 CPUs (CPU 0 and CPU 2). How do I enabled the second cores on the CPU's or are

Re: Dual core CPU's, but only 2 CPU's in-use?

On Sun, 24 Feb 2008 12:46:23 +0100 Dominic Fandrey [EMAIL PROTECTED] wrote: Tigger wrote: Hello. I have a Xeon system with 2 CPU's installed (dual-cores). Under FreeBSD 6.2, a systat reported 4 CPUs in use and so did dmesg. Under FreeBSD 6.3, dmesg is reporting the 4 CPUs, but systat

unexpected result from sh script with `date`

Hello, the following simply sh script is outputting unexpected results. Any idea why? --script-- #!/bin/sh started=`date` echo Started at: $started echo Finished : `date` exit --output-- Started at: Fri Feb 2 22:13:51 EST 2007 Finished : Fri Feb 2 22:13:51 EST 2007 --problem-- Between