From: Geoffrey D. Bennett (g_at_netcraft.com.au)
Date: Wed 18 Dec 2002 - 03:01:09 GMT

• Previous message: Herbert Poetzl: "[vserver] Incident Reporting ..."
• In reply to: Herbert Poetzl: "[vserver] Incident Reporting ..."
• Next in thread: Marcel de Riedmatten: "Re: [vserver] Incident Reporting ..."
• Next in thread: Adam H. Pendleton: "Re: [vserver] ipchains etal. again!"
• Reply: Marcel de Riedmatten: "Re: [vserver] Incident Reporting ..."

On Wed, Dec 18, 2002 at 03:27:53AM +0100, Herbert Poetzl wrote:
>
> hi all!
>
> I spend some time, thinking about the crash reports,
> and made a report/form I would like to propose for all
> uptime/crash reports ...
[...]
> SMP Yes/No
> RAID* No, Raid0, Raid1, Raid5, Raid10, ...
> IOSS* ATA-33, ATA-66, ATA-100, ATA-133, SCSI, SCSI-2, SCSI-3, ...
>
> NIC* 3Com XYZ, Tulip ABC, ...

In some cases, the driver used can also be important (eg. I had the
eepro100 driver crashing reliably whereas the e100 driver worked
great).

-- 
Geoffrey D. Bennett, RHCE, RHCX               geoffrey_at_netcraft.com.au
Senior Systems Engineer           http://www.netcraft.com.au/geoffrey/
NetCraft Australia Pty Ltd           http://www.netcraft.com.au/linux/

• Previous message: Herbert Poetzl: "[vserver] Incident Reporting ..."
• In reply to: Herbert Poetzl: "[vserver] Incident Reporting ..."
• Next in thread: Marcel de Riedmatten: "Re: [vserver] Incident Reporting ..."
• Next in thread: Adam H. Pendleton: "Re: [vserver] ipchains etal. again!"
• Reply: Marcel de Riedmatten: "Re: [vserver] Incident Reporting ..."