You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Hanspeter Roth <ha...@rootshell.be> on 2004/11/14 19:08:53 UTC
Score 9.9 by configuration?
Hello,
I have attached a message that has got 9.9 points.
Is this score assinged by the default or by a custom configuration?
-Hanspeter
----- Forwarded message from Drew Tomlinson <> -----
From: Drew Tomlinson <>
To: FreeBSD Questions <fr...@freebsd.org>
Subject: ****SPAM(9.9)**** shutdown -r Hangs After Upgrading to 4.10
Date: Sun, 07 Nov 2004 16:08:16 -0800
Message-Id: <41...@mykitchentable.net>
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 3.0.0 (2004-09-13) on boogey.rootshell.be
X-Spam-Level: *********
X-Spam-Status: Yes, score=9.9 required=4.0 tests=BAYES_00,FVGT_TRIPWIRE_BF,
FVGT_TRIPWIRE_CB,FVGT_TRIPWIRE_DJ,FVGT_TRIPWIRE_FX,FVGT_TRIPWIRE_II,
FVGT_TRIPWIRE_KB,FVGT_TRIPWIRE_NP,FVGT_TRIPWIRE_PF,FVGT_TRIPWIRE_SB,
FVGT_TRIPWIRE_SK,FVGT_TRIPWIRE_TK,FVGT_TRIPWIRE_UH,FVGT_TRIPWIRE_XB,
FVGT_TRIPWIRE_XC,FVGT_TRIPWIRE_XF,LOCAL_OBFU_GENERIC,SARE_HEAD_XBEEN,
TW_BF,TW_CB,TW_DJ,TW_DR,TW_II,TW_SB,TW_SK,TW_UH,TW_XB,TW_XC,TW_XF
autolearn=no version=3.0.0
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----------=_418EB903.359B433A"
Content-Length: 15125
Lines: 334
Checker-Version SpamAssassin 3.0.0 (2004-09-13) on boogey.rootshell.be
Content analysis details: (9.9 points, 4.0 required, autolearn=no)
pts rule name description
---- ----------------------------------------------------------------
0.1 TW_XC BODY: Odd Letter Triples with XC
1.8 LOCAL_OBFU_GENERIC BODY: Obfuscated 'GENERIC' in body
0.1 TW_BF BODY: Odd Letter Triples with BF
0.1 TW_II BODY: Odd Letter Triples with II
0.1 TW_UH BODY: Odd Letter Triples with UH
0.1 TW_DJ BODY: Odd Letter Triples with DJ
0.1 TW_XF BODY: Odd Letter Triples with XF
0.1 TW_XB BODY: Odd Letter Triples with XB
0.1 TW_SK BODY: Odd Letter Triples with SK
0.1 TW_CB BODY: Odd Letter Triples with CB
0.1 TW_SB BODY: Odd Letter Triples with SB
0.1 TW_DR BODY: Odd Letter Triples with DR
-2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1%
[score: 0.0000]
-0.6 SARE_HEAD_XBEEN Mailng list header found, frequent ham sign
0.7 FVGT_TRIPWIRE_CB FVGT_TRIPWIRE_CB
0.7 FVGT_TRIPWIRE_PF FVGT_TRIPWIRE_PF
0.7 FVGT_TRIPWIRE_UH FVGT_TRIPWIRE_UH
0.7 FVGT_TRIPWIRE_II FVGT_TRIPWIRE_II
0.7 FVGT_TRIPWIRE_XC FVGT_TRIPWIRE_XC
0.7 FVGT_TRIPWIRE_NP FVGT_TRIPWIRE_NP
0.7 FVGT_TRIPWIRE_KB FVGT_TRIPWIRE_KB
0.7 FVGT_TRIPWIRE_SK FVGT_TRIPWIRE_SK
0.7 FVGT_TRIPWIRE_XB FVGT_TRIPWIRE_XB
0.7 FVGT_TRIPWIRE_BF FVGT_TRIPWIRE_BF
0.7 FVGT_TRIPWIRE_DJ FVGT_TRIPWIRE_DJ
0.7 FVGT_TRIPWIRE_FX FVGT_TRIPWIRE_FX
0.7 FVGT_TRIPWIRE_SB FVGT_TRIPWIRE_SB
0.7 FVGT_TRIPWIRE_XF FVGT_TRIPWIRE_XF
0.7 FVGT_TRIPWIRE_TK FVGT_TRIPWIRE_TK
Received: from mx2.freebsd.org (mx2.freebsd.org [216.136.204.119])
by boogey.rootshell.be (Postfix) with ESMTP id 4A1002D55F
for <ha...@rootshell.be>; Mon, 8 Nov 2004 01:08:31 +0100 (CET)
Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18])
by mx2.freebsd.org (Postfix) with ESMTP
id 15C6257BA6; Mon, 8 Nov 2004 00:08:19 +0000 (GMT)
(envelope-from owner-freebsd-questions@freebsd.org)
Received: from hub.freebsd.org (localhost [127.0.0.1])
by hub.freebsd.org (Postfix) with ESMTP
id 7CE5616A4EA; Mon, 8 Nov 2004 00:08:17 +0000 (GMT)
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP id 335AB16A4CE
for <fr...@freebsd.org>;
Mon, 8 Nov 2004 00:08:11 +0000 (GMT)
Received: from relay04.roc.ny.frontiernet.net (relay04.roc.ny.frontiernet.net
[66.133.131.37])
by mx1.FreeBSD.org (Postfix) with ESMTP id A005D43D48
for <fr...@freebsd.org>;
Mon, 8 Nov 2004 00:08:10 +0000 (GMT)
(envelope-from drew@mykitchentable.net)
Received: from filter02.roc.ny.frontiernet.net
(filter02.roc.ny.frontiernet.net [66.133.131.177])
by relay04.roc.ny.frontiernet.net (Postfix) with ESMTP id 262D110285
for <fr...@freebsd.org>;
Mon, 8 Nov 2004 00:08:10 +0000 (UTC)
Received: from relay04.roc.ny.frontiernet.net ([66.133.131.37])
[66.133.131.177]) (amavisd-new, port 10024)
with LMTP id 14623-07-8 for <fr...@freebsd.org>;
Mon, 8 Nov 2004 00:08:10 +0000 (UTC)
Received: from blacklamb.mykitchentable.net
(67-137-46-138.dsl2.elk.ca.frontiernet.net [67.137.46.138])
by relay04.roc.ny.frontiernet.net (Postfix) with ESMTP id 1AD6C101A9
for <fr...@freebsd.org>;
Mon, 8 Nov 2004 00:08:08 +0000 (UTC)
Received: from [192.168.1.25] (lugalong.mykitchentable.net [192.168.1.25])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(No client certificate requested)
by blacklamb.mykitchentable.net (Postfix) with ESMTP id 298EB3BF356
for <fr...@freebsd.org>;
Sun, 7 Nov 2004 16:08:06 -0800 (PST)
Message-ID: <41...@mykitchentable.net>
Date: Sun, 07 Nov 2004 16:08:16 -0800
From: Drew Tomlinson <dr...@mykitchentable.net>
User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: FreeBSD Questions <fr...@freebsd.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new-20040701 (2.0) (Debian) at
filter02.roc.ny.frontiernet.net
Subject: shutdown -r Hangs After Upgrading to 4.10
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <ma...@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
Sender: owner-freebsd-questions@freebsd.org
Errors-To: owner-freebsd-questions@freebsd.org
I've been happily using 4.9-RELEASE-p4 since April 2004. Then,
I decided to upgrade to 4.10-RELEASE-p3 to fix the pthreads problem
since I added an external tape drive to the QLogic SCSI card
that was already in my system.
Anyway, after upgrading, I experienced the same shutdown hanging
symptoms as described in this message:
http://lists.freebsd.org/pipermail/freebsd-current/2003-December/016933.html
In reading the thread, it seems there was an infinite loop problem in
the ahc driver code that was fixed later by Justin Gibbs. So I tried
upgrading to 4-STABLE to see if the problem was fixed there. But I
still have the same symptoms.
I also see these "odd" processes in my ps output:
root 34 0.0 0.0 212 40 ?? Is 10:19PM 0:00.00 adjkerntz
root 20 0.0 0.0 596 48 ?? DLs 10:08PM 0:00.02 vinum
root 13 0.0 0.0 0 0 ?? DL 10:08PM 0:00.04 vnlru
root 12 0.0 0.0 0 0 ?? DL 10:08PM 0:01.39 syncer
root 11 0.0 0.0 0 0 ?? DL 10:08PM 0:00.26 bufdaemon
root 10 0.0 0.0 0 0 ?? DL 10:08PM 0:00.00 vmdaemon
root 9 0.0 0.0 0 0 ?? DL 10:08PM 0:00.73
pagedaemon
root 8 0.0 0.0 0 0 ?? DL 10:08PM 0:00.00
aic_recovery1
root 7 0.0 0.0 0 0 ?? DL 10:08PM 0:00.00
aic_recovery1
root 6 0.0 0.0 0 0 ?? DL 10:08PM 0:00.00
aic_recovery0
root 5 0.0 0.0 0 0 ?? DL 10:08PM 0:00.00
aic_recovery0
root 4 0.0 0.0 0 0 ?? DL 10:08PM 0:00.00 usbtask
root 3 0.0 0.0 0 0 ?? DL 10:08PM 0:00.00 usb0
root 2 0.0 0.0 0 0 ?? DL 10:08PM 0:00.00 taskqueue
root 1 0.0 0.1 552 128 ?? ILs 10:08PM 0:00.01 init
root 0 0.0 0.0 0 0 ?? DLs 10:08PM 0:00.00 swapper
I find them "odd" because the system was powered off/on at 6:19AM after
the machine was shutdown at about 10:08PM. (I tried waiting overnight
to see if it would actually finish it's shutdown.)
And finally, I have one vinum volume that has problems. However after
the system comes up, I can remove and re-create the volume and all of my
data is intact.
I'm assuming that if I get the shutdown issue resolved, these other
problems will heal themselves. I'd appreciate any advice you might have
on how to get my system running on 4.10. My dmesg output follows.
Please let me know if there's any other info I can provide.
Thanks,
Drew
-----
blacklamb# uname -a
FreeBSD blacklamb.mykitchentable.net 4.10-STABLE FreeBSD 4.10-STABLE #0:
Sun Oct 31 21:23:11 PST 2004
tomlinson_dr@blacklamb.mykitchentable.net:/usr/obj/usr/src/sys/BLACKLAMB
i386
blacklamb# dmesg
Copyright (c) 1992-2004 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 4.10-STABLE #0: Sun Oct 31 21:23:11 PST 2004
tomlinson_dr@blacklamb.mykitchentable.net:/usr/obj/usr/src/sys/BLACKLAMB
Timecounter "i8254" frequency 1193182 Hz
CPU: Pentium III/Pentium III Xeon/Celeron (601.37-MHz 686-class CPU)
Origin = "GenuineIntel" Id = 0x673 Stepping = 3
Features=0x387fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,PN,MMX,FXSR,SSE>
real memory = 201261056 (196544K bytes)
config> # di pcic0
Invalid command or syntax. Type `?' for help.
config> # di ata1
Invalid command or syntax. Type `?' for help.
config> # di ata0
Invalid command or syntax. Type `?' for help.
config> # di aic0
Invalid command or syntax. Type `?' for help.
config> # di adv0
Invalid command or syntax. Type `?' for help.
config> q
avail memory = 191930368 (187432K bytes)
Programming 24 pins in IOAPIC #0
IOAPIC #0 intpin 2 -> irq 0
FreeBSD/SMP: Multiprocessor motherboard: 2 CPUs
cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000
cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000
io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000
Preloaded elf kernel "kernel" at 0xc03bb000.
Preloaded userconfig_script "/boot/kernel.conf" at 0xc03bb09c.
Preloaded elf module "ispfw.ko" at 0xc03bb0ec.
Pentium Pro MTRR support enabled
md0: Malloc disk
Using $PIR table, 11 entries at 0xc00fdf10
npx0: <math processor> on motherboard
npx0: INT 16 interface
pcib0: <Intel 82443BX (440 BX) host to PCI bridge> on motherboard
IOAPIC #0 intpin 19 -> irq 2
IOAPIC #0 intpin 18 -> irq 5
IOAPIC #0 intpin 17 -> irq 10
IOAPIC #0 intpin 16 -> irq 11
pci0: <PCI bus> on pcib0
pcib1: <Intel 82443BX (440 BX) PCI-PCI (AGP) bridge> at device 1.0 on pci0
pci1: <PCI bus> on pcib1
pci1: <ATI Mach64-GZ graphics accelerator> at 0.0
isab0: <Intel 82371AB PCI to ISA bridge> at device 4.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel PIIX4 ATA33 controller> port 0x1c90-0x1c9f at device 4.1
on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
uhci0: <Intel 82371AB/EB (PIIX4) USB controller> port 0x1ca0-0x1cbf irq
2 at device 4.2 on pci0
usb0: <Intel 82371AB/EB (PIIX4) USB controller> on uhci0
usb0: USB revision 1.0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
Timecounter "PIIX" frequency 3579545 Hz
chip1: <Intel 82371AB Power management controller> port 0xe800-0xe80f at
device 4.3 on pci0
ahc0: <Adaptec aic7895 Ultra SCSI adapter> port 0x1000-0x10ff mem
0xfc100000-0xfc100fff irq 5 at device 5.0 on pci0
ahc0: Using left over BIOS settings
aic7895C: Ultra Wide Channel A, SCSI Id=7, 32/253 SCBs
ahc1: <Adaptec aic7895 Ultra SCSI adapter> port 0x1400-0x14ff mem
0xfc101000-0xfc101fff irq 5 at device 5.1 on pci0
ahc1: Host Adapter Bios disabled. Using default SCSI device parameters
aic7895C: Ultra Wide Channel B, SCSI Id=7, 32/253 SCBs
fxp0: <Intel 82559 Pro/100 Ethernet> port 0x1cc0-0x1cff mem
0xfc000000-0xfc0fffff,0xfc102000-0xfc102fff irq 2 at device 6.0 on pci0
fxp0: Ethernet address 00:e0:18:c4:f4:5e
inphy0: <i82555 10/100 media interface> on miibus0
inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
isp0: <Qlogic ISP 1020/1040 PCI SCSI Adapter> port 0x1800-0x18ff mem
0xfc103000-0xfc103fff irq 10 at device 9.0 on pci0
fwohci0: <VIA VT6306> port 0x1c00-0x1c7f mem 0xfc104000-0xfc1047ff irq
11 at device 10.0 on pci0
fwohci0: OHCI version 1.0 (ROM=1)
fwohci0: No. of Isochronous channel is 8.
fwohci0: EUI64 00:40:63:00:00:00:07:ff
fwohci0: Phy 1394a available S400, 3 ports.
fwohci0: Link S400, max_rec 2048 bytes.
firewire0: <IEEE1394(FireWire) bus> on fwohci0
sbp0: <SBP-2/SCSI over FireWire> on firewire0
fwe0: <Ethernet over FireWire> on firewire0
if_fwe0: Fake Ethernet address: 02:40:63:00:07:ff
fwohci0: Initiate bus reset
fwohci0: node_id=0xc800ffc1, gen=1, CYCLEMASTER mode
firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 (me)
firewire0: bus manager 1 (me)
pcib2: <DEC 21152 PCI-PCI bridge> at device 12.0 on pci0
pci2: <PCI bus> on pcib2
orm0: <Option ROMs> at iomem 0xc0000-0xc7fff,0xc8000-0xcd7ff on isa0
pmtimer0 on isa0
fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x100>
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A, console
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0
ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
ppi0: <Parallel I/O> on ppbus0
APIC_IO: Testing 8254 interrupt delivery
APIC_IO: routing 8254 via IOAPIC #0 intpin 2
SMP: AP CPU #1 Launched!
ad0: 76319MB <GENERIC GENERIC> [155061/16/63] at ata0-master UDMA33
ad1: 76319MB <WDC WD800AB-22CBA0> [155061/16/63] at ata0-slave UDMA33
acd0: CDROM <HITACHI CDR-8435> at ata1-master PIO4
Waiting 10 seconds for SCSI devices to settle
firewire0: New S400 device ID:00d04b0ce0100707
sa0 at isp0 bus 0 target 6 lun 0
sa0: <DEC DLT2000 840F> Removable Sequential Access SCSI-2 device
sa0: 3.300MB/s transfers
da0 at ahc0 bus 0 target 0 lun 0
da0: <SEAGATE SX19171W 9D32> Fixed Direct Access SCSI-2 device
da0: 11.626MB/s transfers (5.813MHz, offset 8, 16bit), Tagged Queueing
Enabled
da0: 8683MB (17783112 512 byte sectors: 64H 32S/T 8683C)
da1 at ahc0 bus 0 target 2 lun 0
da1: <SEAGATE SX19171W 9D32> Fixed Direct Access SCSI-2 device
da1: 11.626MB/s transfers (5.813MHz, offset 8, 16bit), Tagged Queueing
Enabled
da1: 8683MB (17783112 512 byte sectors: 64H 32S/T 8683C)
da2 at sbp0 bus 0 target 0 lun 0
da2: <Oxford 911G 0135> Fixed Simplified Direct Access SCSI-4 device
da2: 50.000MB/s transfers
da2: 76351MB (156368016 512 byte sectors: 255H 63S/T 9733C)
Mounting root from ufs:/dev/da0s1a
vinum: drive backup is down
vinum: removing backup.p0.s0
vinum: backup.p0 is up
vinum: backup is up
vinum: removing backup.p0
vinum: backup is down
vinum: removing backup
vinum: drive backup is up
vinum: backup.p0.s0 is up
vinum: backup.p0 is up
vinum: backup is up
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
----- End forwarded message -----
Re: Score 9.9 by configuration?
Posted by JamesDR <ro...@bellsouth.net>.
Whats the issue here? Adding the scores comes to 10.2, but i haven't
looked at the score set to determine what the exact precision was on
each of those decimals.
This is the score chart:
0.1
1.8
0.1
0.1
0.1
0.1
0.1
0.1
0.1
0.1
0.1
0.1
-2.6
-0.6
0.7
0.7
0.7
0.7
0.7
0.7
0.7
0.7
0.7
0.7
0.7
0.7
0.7
0.7
0.7
TOTAL: 10.2
I guess I'm missing the problem here. (other than at first glance
calculation is incorrect by .3)
Thanks,
JamesDR
Hanspeter Roth wrote:
> Hello,
>
> I have attached a message that has got 9.9 points.
> Is this score assinged by the default or by a custom configuration?
>
> -Hanspeter
>
>
> ----- Forwarded message from Drew Tomlinson <> -----
>
> From: Drew Tomlinson <>
> To: FreeBSD Questions <fr...@freebsd.org>
> Subject: ****SPAM(9.9)**** shutdown -r Hangs After Upgrading to 4.10
> Date: Sun, 07 Nov 2004 16:08:16 -0800
> Message-Id: <41...@mykitchentable.net>
> X-Spam-Flag: YES
> X-Spam-Checker-Version: SpamAssassin 3.0.0 (2004-09-13) on boogey.rootshell.be
> X-Spam-Level: *********
> X-Spam-Status: Yes, score=9.9 required=4.0 tests=BAYES_00,FVGT_TRIPWIRE_BF,
> FVGT_TRIPWIRE_CB,FVGT_TRIPWIRE_DJ,FVGT_TRIPWIRE_FX,FVGT_TRIPWIRE_II,
> FVGT_TRIPWIRE_KB,FVGT_TRIPWIRE_NP,FVGT_TRIPWIRE_PF,FVGT_TRIPWIRE_SB,
> FVGT_TRIPWIRE_SK,FVGT_TRIPWIRE_TK,FVGT_TRIPWIRE_UH,FVGT_TRIPWIRE_XB,
> FVGT_TRIPWIRE_XC,FVGT_TRIPWIRE_XF,LOCAL_OBFU_GENERIC,SARE_HEAD_XBEEN,
> TW_BF,TW_CB,TW_DJ,TW_DR,TW_II,TW_SB,TW_SK,TW_UH,TW_XB,TW_XC,TW_XF
> autolearn=no version=3.0.0
> MIME-Version: 1.0
> Content-Type: multipart/mixed; boundary="----------=_418EB903.359B433A"
> Content-Length: 15125
> Lines: 334
>
> Checker-Version SpamAssassin 3.0.0 (2004-09-13) on boogey.rootshell.be
> Content analysis details: (9.9 points, 4.0 required, autolearn=no)
>
> pts rule name description
> ---- ----------------------------------------------------------------
> 0.1 TW_XC BODY: Odd Letter Triples with XC
> 1.8 LOCAL_OBFU_GENERIC BODY: Obfuscated 'GENERIC' in body
> 0.1 TW_BF BODY: Odd Letter Triples with BF
> 0.1 TW_II BODY: Odd Letter Triples with II
> 0.1 TW_UH BODY: Odd Letter Triples with UH
> 0.1 TW_DJ BODY: Odd Letter Triples with DJ
> 0.1 TW_XF BODY: Odd Letter Triples with XF
> 0.1 TW_XB BODY: Odd Letter Triples with XB
> 0.1 TW_SK BODY: Odd Letter Triples with SK
> 0.1 TW_CB BODY: Odd Letter Triples with CB
> 0.1 TW_SB BODY: Odd Letter Triples with SB
> 0.1 TW_DR BODY: Odd Letter Triples with DR
> -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1%
> [score: 0.0000]
> -0.6 SARE_HEAD_XBEEN Mailng list header found, frequent ham sign
> 0.7 FVGT_TRIPWIRE_CB FVGT_TRIPWIRE_CB
> 0.7 FVGT_TRIPWIRE_PF FVGT_TRIPWIRE_PF
> 0.7 FVGT_TRIPWIRE_UH FVGT_TRIPWIRE_UH
> 0.7 FVGT_TRIPWIRE_II FVGT_TRIPWIRE_II
> 0.7 FVGT_TRIPWIRE_XC FVGT_TRIPWIRE_XC
> 0.7 FVGT_TRIPWIRE_NP FVGT_TRIPWIRE_NP
> 0.7 FVGT_TRIPWIRE_KB FVGT_TRIPWIRE_KB
> 0.7 FVGT_TRIPWIRE_SK FVGT_TRIPWIRE_SK
> 0.7 FVGT_TRIPWIRE_XB FVGT_TRIPWIRE_XB
> 0.7 FVGT_TRIPWIRE_BF FVGT_TRIPWIRE_BF
> 0.7 FVGT_TRIPWIRE_DJ FVGT_TRIPWIRE_DJ
> 0.7 FVGT_TRIPWIRE_FX FVGT_TRIPWIRE_FX
> 0.7 FVGT_TRIPWIRE_SB FVGT_TRIPWIRE_SB
> 0.7 FVGT_TRIPWIRE_XF FVGT_TRIPWIRE_XF
> 0.7 FVGT_TRIPWIRE_TK FVGT_TRIPWIRE_TK
>
>
>
> Received: from mx2.freebsd.org (mx2.freebsd.org [216.136.204.119])
> by boogey.rootshell.be (Postfix) with ESMTP id 4A1002D55F
> for <ha...@rootshell.be>; Mon, 8 Nov 2004 01:08:31 +0100 (CET)
> Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18])
> by mx2.freebsd.org (Postfix) with ESMTP
> id 15C6257BA6; Mon, 8 Nov 2004 00:08:19 +0000 (GMT)
> (envelope-from owner-freebsd-questions@freebsd.org)
> Received: from hub.freebsd.org (localhost [127.0.0.1])
> by hub.freebsd.org (Postfix) with ESMTP
> id 7CE5616A4EA; Mon, 8 Nov 2004 00:08:17 +0000 (GMT)
> Delivered-To: freebsd-questions@freebsd.org
> Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
> by hub.freebsd.org (Postfix) with ESMTP id 335AB16A4CE
> for <fr...@freebsd.org>;
> Mon, 8 Nov 2004 00:08:11 +0000 (GMT)
> Received: from relay04.roc.ny.frontiernet.net (relay04.roc.ny.frontiernet.net
> [66.133.131.37])
> by mx1.FreeBSD.org (Postfix) with ESMTP id A005D43D48
> for <fr...@freebsd.org>;
> Mon, 8 Nov 2004 00:08:10 +0000 (GMT)
> (envelope-from drew@mykitchentable.net)
> Received: from filter02.roc.ny.frontiernet.net
> (filter02.roc.ny.frontiernet.net [66.133.131.177])
> by relay04.roc.ny.frontiernet.net (Postfix) with ESMTP id 262D110285
> for <fr...@freebsd.org>;
> Mon, 8 Nov 2004 00:08:10 +0000 (UTC)
> Received: from relay04.roc.ny.frontiernet.net ([66.133.131.37])
> [66.133.131.177]) (amavisd-new, port 10024)
> with LMTP id 14623-07-8 for <fr...@freebsd.org>;
> Mon, 8 Nov 2004 00:08:10 +0000 (UTC)
> Received: from blacklamb.mykitchentable.net
> (67-137-46-138.dsl2.elk.ca.frontiernet.net [67.137.46.138])
> by relay04.roc.ny.frontiernet.net (Postfix) with ESMTP id 1AD6C101A9
> for <fr...@freebsd.org>;
> Mon, 8 Nov 2004 00:08:08 +0000 (UTC)
> Received: from [192.168.1.25] (lugalong.mykitchentable.net [192.168.1.25])
> (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
> (No client certificate requested)
> by blacklamb.mykitchentable.net (Postfix) with ESMTP id 298EB3BF356
> for <fr...@freebsd.org>;
> Sun, 7 Nov 2004 16:08:06 -0800 (PST)
> Message-ID: <41...@mykitchentable.net>
> Date: Sun, 07 Nov 2004 16:08:16 -0800
> From: Drew Tomlinson <dr...@mykitchentable.net>
> User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913)
> X-Accept-Language: en-us, en
> MIME-Version: 1.0
> To: FreeBSD Questions <fr...@freebsd.org>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> Content-Transfer-Encoding: 7bit
> X-Virus-Scanned: by amavisd-new-20040701 (2.0) (Debian) at
> filter02.roc.ny.frontiernet.net
> Subject: shutdown -r Hangs After Upgrading to 4.10
> X-BeenThere: freebsd-questions@freebsd.org
> X-Mailman-Version: 2.1.1
> Precedence: list
> List-Id: User questions <freebsd-questions.freebsd.org>
> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
> <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
> List-Post: <ma...@freebsd.org>
> List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
> <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
> Sender: owner-freebsd-questions@freebsd.org
> Errors-To: owner-freebsd-questions@freebsd.org
>
> I've been happily using 4.9-RELEASE-p4 since April 2004. Then,
> I decided to upgrade to 4.10-RELEASE-p3 to fix the pthreads problem
> since I added an external tape drive to the QLogic SCSI card
> that was already in my system.
>
> Anyway, after upgrading, I experienced the same shutdown hanging
> symptoms as described in this message:
>
> http://lists.freebsd.org/pipermail/freebsd-current/2003-December/016933.html
>
>
> In reading the thread, it seems there was an infinite loop problem in
> the ahc driver code that was fixed later by Justin Gibbs. So I tried
> upgrading to 4-STABLE to see if the problem was fixed there. But I
> still have the same symptoms.
>
> I also see these "odd" processes in my ps output:
>
> root 34 0.0 0.0 212 40 ?? Is 10:19PM 0:00.00 adjkerntz
> root 20 0.0 0.0 596 48 ?? DLs 10:08PM 0:00.02 vinum
> root 13 0.0 0.0 0 0 ?? DL 10:08PM 0:00.04 vnlru
> root 12 0.0 0.0 0 0 ?? DL 10:08PM 0:01.39 syncer
> root 11 0.0 0.0 0 0 ?? DL 10:08PM 0:00.26 bufdaemon
> root 10 0.0 0.0 0 0 ?? DL 10:08PM 0:00.00 vmdaemon
> root 9 0.0 0.0 0 0 ?? DL 10:08PM 0:00.73
> pagedaemon
> root 8 0.0 0.0 0 0 ?? DL 10:08PM 0:00.00
> aic_recovery1
> root 7 0.0 0.0 0 0 ?? DL 10:08PM 0:00.00
> aic_recovery1
> root 6 0.0 0.0 0 0 ?? DL 10:08PM 0:00.00
> aic_recovery0
> root 5 0.0 0.0 0 0 ?? DL 10:08PM 0:00.00
> aic_recovery0
> root 4 0.0 0.0 0 0 ?? DL 10:08PM 0:00.00 usbtask
> root 3 0.0 0.0 0 0 ?? DL 10:08PM 0:00.00 usb0
> root 2 0.0 0.0 0 0 ?? DL 10:08PM 0:00.00 taskqueue
> root 1 0.0 0.1 552 128 ?? ILs 10:08PM 0:00.01 init
> root 0 0.0 0.0 0 0 ?? DLs 10:08PM 0:00.00 swapper
>
> I find them "odd" because the system was powered off/on at 6:19AM after
> the machine was shutdown at about 10:08PM. (I tried waiting overnight
> to see if it would actually finish it's shutdown.)
>
> And finally, I have one vinum volume that has problems. However after
> the system comes up, I can remove and re-create the volume and all of my
> data is intact.
>
> I'm assuming that if I get the shutdown issue resolved, these other
> problems will heal themselves. I'd appreciate any advice you might have
> on how to get my system running on 4.10. My dmesg output follows.
> Please let me know if there's any other info I can provide.
>
> Thanks,
>
> Drew
>
> -----
> blacklamb# uname -a
> FreeBSD blacklamb.mykitchentable.net 4.10-STABLE FreeBSD 4.10-STABLE #0:
> Sun Oct 31 21:23:11 PST 2004
> tomlinson_dr@blacklamb.mykitchentable.net:/usr/obj/usr/src/sys/BLACKLAMB
> i386
>
> blacklamb# dmesg
> Copyright (c) 1992-2004 The FreeBSD Project.
> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
> The Regents of the University of California. All rights reserved.
> FreeBSD 4.10-STABLE #0: Sun Oct 31 21:23:11 PST 2004
> tomlinson_dr@blacklamb.mykitchentable.net:/usr/obj/usr/src/sys/BLACKLAMB
> Timecounter "i8254" frequency 1193182 Hz
> CPU: Pentium III/Pentium III Xeon/Celeron (601.37-MHz 686-class CPU)
> Origin = "GenuineIntel" Id = 0x673 Stepping = 3
>
> Features=0x387fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,PN,MMX,FXSR,SSE>
>
> real memory = 201261056 (196544K bytes)
> config> # di pcic0
> Invalid command or syntax. Type `?' for help.
> config> # di ata1
> Invalid command or syntax. Type `?' for help.
> config> # di ata0
> Invalid command or syntax. Type `?' for help.
> config> # di aic0
> Invalid command or syntax. Type `?' for help.
> config> # di adv0
> Invalid command or syntax. Type `?' for help.
> config> q
> avail memory = 191930368 (187432K bytes)
> Programming 24 pins in IOAPIC #0
> IOAPIC #0 intpin 2 -> irq 0
> FreeBSD/SMP: Multiprocessor motherboard: 2 CPUs
> cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000
> cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000
> io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000
> Preloaded elf kernel "kernel" at 0xc03bb000.
> Preloaded userconfig_script "/boot/kernel.conf" at 0xc03bb09c.
> Preloaded elf module "ispfw.ko" at 0xc03bb0ec.
> Pentium Pro MTRR support enabled
> md0: Malloc disk
> Using $PIR table, 11 entries at 0xc00fdf10
> npx0: <math processor> on motherboard
> npx0: INT 16 interface
> pcib0: <Intel 82443BX (440 BX) host to PCI bridge> on motherboard
> IOAPIC #0 intpin 19 -> irq 2
> IOAPIC #0 intpin 18 -> irq 5
> IOAPIC #0 intpin 17 -> irq 10
> IOAPIC #0 intpin 16 -> irq 11
> pci0: <PCI bus> on pcib0
> pcib1: <Intel 82443BX (440 BX) PCI-PCI (AGP) bridge> at device 1.0 on pci0
> pci1: <PCI bus> on pcib1
> pci1: <ATI Mach64-GZ graphics accelerator> at 0.0
> isab0: <Intel 82371AB PCI to ISA bridge> at device 4.0 on pci0
> isa0: <ISA bus> on isab0
> atapci0: <Intel PIIX4 ATA33 controller> port 0x1c90-0x1c9f at device 4.1
> on pci0
> ata0: at 0x1f0 irq 14 on atapci0
> ata1: at 0x170 irq 15 on atapci0
> uhci0: <Intel 82371AB/EB (PIIX4) USB controller> port 0x1ca0-0x1cbf irq
> 2 at device 4.2 on pci0
> usb0: <Intel 82371AB/EB (PIIX4) USB controller> on uhci0
> usb0: USB revision 1.0
> uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
> uhub0: 2 ports with 2 removable, self powered
> Timecounter "PIIX" frequency 3579545 Hz
> chip1: <Intel 82371AB Power management controller> port 0xe800-0xe80f at
> device 4.3 on pci0
> ahc0: <Adaptec aic7895 Ultra SCSI adapter> port 0x1000-0x10ff mem
> 0xfc100000-0xfc100fff irq 5 at device 5.0 on pci0
> ahc0: Using left over BIOS settings
> aic7895C: Ultra Wide Channel A, SCSI Id=7, 32/253 SCBs
> ahc1: <Adaptec aic7895 Ultra SCSI adapter> port 0x1400-0x14ff mem
> 0xfc101000-0xfc101fff irq 5 at device 5.1 on pci0
> ahc1: Host Adapter Bios disabled. Using default SCSI device parameters
> aic7895C: Ultra Wide Channel B, SCSI Id=7, 32/253 SCBs
> fxp0: <Intel 82559 Pro/100 Ethernet> port 0x1cc0-0x1cff mem
> 0xfc000000-0xfc0fffff,0xfc102000-0xfc102fff irq 2 at device 6.0 on pci0
> fxp0: Ethernet address 00:e0:18:c4:f4:5e
> inphy0: <i82555 10/100 media interface> on miibus0
> inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> isp0: <Qlogic ISP 1020/1040 PCI SCSI Adapter> port 0x1800-0x18ff mem
> 0xfc103000-0xfc103fff irq 10 at device 9.0 on pci0
> fwohci0: <VIA VT6306> port 0x1c00-0x1c7f mem 0xfc104000-0xfc1047ff irq
> 11 at device 10.0 on pci0
> fwohci0: OHCI version 1.0 (ROM=1)
> fwohci0: No. of Isochronous channel is 8.
> fwohci0: EUI64 00:40:63:00:00:00:07:ff
> fwohci0: Phy 1394a available S400, 3 ports.
> fwohci0: Link S400, max_rec 2048 bytes.
> firewire0: <IEEE1394(FireWire) bus> on fwohci0
> sbp0: <SBP-2/SCSI over FireWire> on firewire0
> fwe0: <Ethernet over FireWire> on firewire0
> if_fwe0: Fake Ethernet address: 02:40:63:00:07:ff
> fwohci0: Initiate bus reset
> fwohci0: node_id=0xc800ffc1, gen=1, CYCLEMASTER mode
> firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 (me)
> firewire0: bus manager 1 (me)
> pcib2: <DEC 21152 PCI-PCI bridge> at device 12.0 on pci0
> pci2: <PCI bus> on pcib2
> orm0: <Option ROMs> at iomem 0xc0000-0xc7fff,0xc8000-0xcd7ff on isa0
> pmtimer0 on isa0
> fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
> fdc0: FIFO enabled, 8 bytes threshold
> fd0: <1440-KB 3.5" drive> on fdc0 drive 0
> atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
> vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
> sc0: <System console> at flags 0x100 on isa0
> sc0: VGA <16 virtual consoles, flags=0x100>
> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
> sio0: type 16550A, console
> sio1 at port 0x2f8-0x2ff irq 3 on isa0
> sio1: type 16550A
> ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0
> ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
> lpt0: <Printer> on ppbus0
> lpt0: Interrupt-driven port
> ppi0: <Parallel I/O> on ppbus0
> APIC_IO: Testing 8254 interrupt delivery
> APIC_IO: routing 8254 via IOAPIC #0 intpin 2
> SMP: AP CPU #1 Launched!
> ad0: 76319MB <GENERIC GENERIC> [155061/16/63] at ata0-master UDMA33
> ad1: 76319MB <WDC WD800AB-22CBA0> [155061/16/63] at ata0-slave UDMA33
> acd0: CDROM <HITACHI CDR-8435> at ata1-master PIO4
> Waiting 10 seconds for SCSI devices to settle
> firewire0: New S400 device ID:00d04b0ce0100707
> sa0 at isp0 bus 0 target 6 lun 0
> sa0: <DEC DLT2000 840F> Removable Sequential Access SCSI-2 device
> sa0: 3.300MB/s transfers
> da0 at ahc0 bus 0 target 0 lun 0
> da0: <SEAGATE SX19171W 9D32> Fixed Direct Access SCSI-2 device
> da0: 11.626MB/s transfers (5.813MHz, offset 8, 16bit), Tagged Queueing
> Enabled
> da0: 8683MB (17783112 512 byte sectors: 64H 32S/T 8683C)
> da1 at ahc0 bus 0 target 2 lun 0
> da1: <SEAGATE SX19171W 9D32> Fixed Direct Access SCSI-2 device
> da1: 11.626MB/s transfers (5.813MHz, offset 8, 16bit), Tagged Queueing
> Enabled
> da1: 8683MB (17783112 512 byte sectors: 64H 32S/T 8683C)
> da2 at sbp0 bus 0 target 0 lun 0
> da2: <Oxford 911G 0135> Fixed Simplified Direct Access SCSI-4 device
> da2: 50.000MB/s transfers
> da2: 76351MB (156368016 512 byte sectors: 255H 63S/T 9733C)
> Mounting root from ufs:/dev/da0s1a
> vinum: drive backup is down
> vinum: removing backup.p0.s0
> vinum: backup.p0 is up
> vinum: backup is up
> vinum: removing backup.p0
> vinum: backup is down
> vinum: removing backup
> vinum: drive backup is up
> vinum: backup.p0.s0 is up
> vinum: backup.p0 is up
> vinum: backup is up
>
> _______________________________________________
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
>
>
> ----- End forwarded message -----
>
Re[2]: Score 9.9 by configuration?
Posted by Robert Menschel <Ro...@Menschel.net>.
Hello Hanspeter,
Monday, November 15, 2004, 3:55:01 AM, you wrote:
HR> On Nov 14 at 21:28, Matt Kettler spoke:
>> Defintiely custom.
>>
>> FVGT_TRIPWIRE_* are add-on rules, and are not a part of the standard SA set.
>> TW_* are also add-on rules. In fact, I suspect they are a duplicate of the
>> same ruleset, but with different names.
>> LOCAL_OBFU generic is a local customization. And a heavy hitter at 1.8
>> points.
>> SARE_HEAD_XBEEN is an add-on.
>>
>> The only "standard" rule in the list of hits is BAYES_00, a nonspam rule.
HR> Ok, thanks for explaining.
HR> If add-ons are added should the `required' level be increased in
HR> order to prevent to much false positives?
IMO: NO.
1) As Matt pointed out, you've duplicated your add-ons -- TW_* /is/
a later version of Tripwire, renamed to shorted the rule list in the
email headers. The first step is to use add-ons correctly, without
duplication, and using those add-ons which apply to your system
without using those that don't.
2) Analyze why the emali was flagged. In addition to the rule
duplication, it was flagged because it's not a "normal" email, but
instead a technical email which has a lot of strange letter
combinations, and it's specifically these strange letter combinations
that Tripwire/TW checks for.
If you expect to process a lot of these strange letter combination
emails, then either a) find some way to bypass SpamAssassin for these
emails (emails from technical lists), or don't use the Tripwire rules.
Except for the duplication, the rules did what they're supposed to.
Increase your threshold to allow for this strange effect (tripwire on
technical email), and you'll let through lots of false negatives.
Bob Menschel
Re: Score 9.9 by configuration?
Posted by Hanspeter Roth <ha...@rootshell.be>.
On Nov 15 at 14:27, Dan Barker spoke:
> Don't remember if you need to do this by user or not. But, if you put the
> zeros in local.cf, it will do the same thing, but for everybody.
local.cf is probably not located in ~/.spamassassin, is it?
But I was told SA is running on a separate box anyway...
-Hanspeter
Re: Score 9.9 by configuration?
Posted by Hanspeter Roth <ha...@rootshell.be>.
On Nov 15 at 22:21, hamann.w@t-online.de spoke:
> >> This were perfect if it were not unsafe.
> >> Doesn't ~/.spamassassin/user_prefs require allow_user_rules=1 ?
> >> It is not recommended. Is there a way to make allow_user_rules safe?
> >>
> >> -Hanspeter
> >>
> Hi,
>
> they will be safe if
> - the prefs are read form a sql database rather than a text file and
> - the front end that writes to the database restricts the data that can be inserted.
Ok. This sounds a little complicated. It doesn't encourage me to
suggest it to my admin.
-Hanspeter
RE: Score 9.9 by configuration?
Posted by Dan Barker <db...@visioncomm.net>.
Don't remember if you need to do this by user or not. But, if you put the
zeros in local.cf, it will do the same thing, but for everybody.
Dan
-----Original Message-----
From: Hanspeter Roth [mailto:hampi@rootshell.be]
Sent: Monday, November 15, 2004 2:23 PM
To: users@spamassassin.apache.org
Subject: Re: Score 9.9 by configuration?
On Nov 15 at 16:57, Martin spoke:
> You could zero out the rules u don't wish to use, so they wont trigger
> further false positives, in your .spamassassin/user_prefs file assuming
you
> have one in your home directory.
This were perfect if it were not unsafe.
Doesn't ~/.spamassassin/user_prefs require allow_user_rules=1 ?
It is not recommended. Is there a way to make allow_user_rules safe?
-Hanspeter
Re: Score 9.9 by configuration?
Posted by Hanspeter Roth <ha...@rootshell.be>.
On Nov 15 at 16:57, Martin spoke:
> You could zero out the rules u don't wish to use, so they wont trigger
> further false positives, in your .spamassassin/user_prefs file assuming you
> have one in your home directory.
This were perfect if it were not unsafe.
Doesn't ~/.spamassassin/user_prefs require allow_user_rules=1 ?
It is not recommended. Is there a way to make allow_user_rules safe?
-Hanspeter
RE: Score 9.9 by configuration?
Posted by Martin <ma...@ntlworld.com>.
|-----Original Message-----
|From: Hanspeter Roth [mailto:hampi@rootshell.be]
|Sent: 15 November 2004 16:13
|To: users@spamassassin.apache.org
|Subject: Re: Score 9.9 by configuration?
|
| On Nov 15 at 08:38, Matt Kettler spoke:
|
|> If you took away the 15 FVGT_TRIPWIRE_* hits the score of
|the message
|> would have gone down by about 10.5 points.
|
|I'm trying to advise the admin. But I don't know his plans...
|
|> Find the duplicates and remove them. My guess is the server has both
|> tripwire.cf (old) and 99_FVGT_Tripwire.cf (new) installed in
|> /etc/mail/spammassassin.
|
|I forgot to mention spamassassin is running on a different
|server. I have no access on that server. (/etc/mail/spamassassin is not
|shared.)
|
|> You could compensate for the misconfig by increasing score
|thresholds,
|> but in this case, poor performance would ensue.
|
|My ~/.procmailrc is processed bye the mail setup. But how
|could I increase the `required' threshold in some kind of
|~/.spamassassinrc?
|(Procmail is restricted. It can't pipe. So I can't pipe to
|spamassassin again.)
|
You could zero out the rules u don't wish to use, so they wont trigger
further false positives, in your .spamassassin/user_prefs file assuming you
have one in your home directory.
Martin
Re: Score 9.9 by configuration?
Posted by Hanspeter Roth <ha...@rootshell.be>.
On Nov 15 at 08:38, Matt Kettler spoke:
> If you took away the 15 FVGT_TRIPWIRE_* hits the score of the message would
> have gone down by about 10.5 points.
I'm trying to advise the admin. But I don't know his plans...
> Find the duplicates and remove them. My guess is the server has both
> tripwire.cf (old) and 99_FVGT_Tripwire.cf (new) installed in
> /etc/mail/spammassassin.
I forgot to mention spamassassin is running on a different server. I
have no access on that server. (/etc/mail/spamassassin is not
shared.)
> You could compensate for the misconfig by increasing score thresholds, but
> in this case, poor performance would ensue.
My ~/.procmailrc is processed bye the mail setup. But how could I
increase the `required' threshold in some kind of ~/.spamassassinrc?
(Procmail is restricted. It can't pipe. So I can't pipe to
spamassassin again.)
-Hanspeter
Re: Score 9.9 by configuration?
Posted by Matt Kettler <mk...@comcast.net>.
At 12:55 PM 11/15/2004 +0100, you wrote:
>Ok, thanks for explaining.
>If add-ons are added should the `required' level be increased in
>order to prevent to much false positives?
Really it depends on what the FP ratio of the added rules are like. Usualy
not, or only very slightly, as most add-ons are mass-checked for FPs and
the scores and/or rules are adjusted accordingly.
The biggest problem I saw with that message is it had two versions of
tripwire, both running at the same time. One older version with roughly 0.7
as a score, one newer one with roughly 0.1 as a score. The current version
has names and scores consistent with the low-scoring version.
http://www.rulesemporium.com/rules/99_FVGT_Tripwire.cf
If you took away the 15 FVGT_TRIPWIRE_* hits the score of the message would
have gone down by about 10.5 points.
Find the duplicates and remove them. My guess is the server has both
tripwire.cf (old) and 99_FVGT_Tripwire.cf (new) installed in
/etc/mail/spammassassin.
You could compensate for the misconfig by increasing score thresholds, but
in this case, poor performance would ensue.
> > Round numbers are just that.. Adding lots of round numbers makes for a lot
> > of rounding error.
>
>Is that to say if there are lots of items which may produce rounding
>errors the `required' level should be increased accordingly?
No.. That error is in Jame's hand calculation of 10.2, not in SA's
calculation of 9.9. It doesn't affect the required thresholds or anything else.
What I'm saying is if you hand-add the rounded numbers SA prints in the
report you can get a different score than SA does. It could be quite a bit
higher or lower, because you're working from a bunch of rounded numbers.
Don't be surprised by this, because you're not adding the real scores out
of the .cf files.
When SA computes the score, it uses all 4 decimal places. SA only rounds
when it prints things in the reports, and that's just to keep the report
from getting cluttered.
Re: Score 9.9 by configuration?
Posted by Hanspeter Roth <ha...@rootshell.be>.
On Nov 14 at 21:28, Matt Kettler spoke:
> Defintiely custom.
>
> FVGT_TRIPWIRE_* are add-on rules, and are not a part of the standard SA set.
> TW_* are also add-on rules. In fact, I suspect they are a duplicate of the
> same ruleset, but with different names.
> LOCAL_OBFU generic is a local customization. And a heavy hitter at 1.8
> points.
> SARE_HEAD_XBEEN is an add-on.
>
> The only "standard" rule in the list of hits is BAYES_00, a nonspam rule.
Ok, thanks for explaining.
If add-ons are added should the `required' level be increased in
order to prevent to much false positives?
>
>
> As for James's concern about 9.9 vs 10.2 score, that much is easily
Well this is some 3%. This doesn't bother me.
What bothers me is that a non-spam message is tagged 9.9 while the
required level is 4.0. This is some 200%.
[...]
> Round numbers are just that.. Adding lots of round numbers makes for a lot
> of rounding error.
Is that to say if there are lots of items which may produce rounding
errors the `required' level should be increased accordingly?
-Hanspeter
Re: Score 9.9 by configuration?
Posted by Matt Kettler <mk...@comcast.net>.
Defintiely custom.
FVGT_TRIPWIRE_* are add-on rules, and are not a part of the standard SA set.
TW_* are also add-on rules. In fact, I suspect they are a duplicate of the
same ruleset, but with different names.
LOCAL_OBFU generic is a local customization. And a heavy hitter at 1.8 points.
SARE_HEAD_XBEEN is an add-on.
The only "standard" rule in the list of hits is BAYES_00, a nonspam rule.
As for James's concern about 9.9 vs 10.2 score, that much is easily
accounted for by rounding. When you only print 2 digits, the actual number
could be appreciably higher. ie: it could be 9.999, which makes the
difference in total score 0.201 compared to 10.2.
With so many numbers in the addition, each printed as a rounded number, all
the 0.1's could really 0.06's and that 0.04 points rounding adds up when
there are 10 hits.. that could be a 0.4 point difference right there.
Don't be surprised when you get big errors when you add a large number or
rounded numbers up when compared with adding all the numbers and then
rounding. There's a lot of room for error there.. In fact, it could be as
much as 0.0499 * the number of hits. With 29 numbers in the addition (I
think that's how many there are here..) , that makes up to 1.4471 points of
difference.
Round numbers are just that.. Adding lots of round numbers makes for a lot
of rounding error.
At 07:08 PM 11/14/2004 +0100, Hanspeter Roth wrote:
>Hello,
>
>I have attached a message that has got 9.9 points.
>Is this score assinged by the default or by a custom configuration?
>
>-Hanspeter
>
>
>----- Forwarded message from Drew Tomlinson <> -----
>
>From: Drew Tomlinson <>
>To: FreeBSD Questions <fr...@freebsd.org>
>Subject: ****SPAM(9.9)**** shutdown -r Hangs After Upgrading to 4.10
>Date: Sun, 07 Nov 2004 16:08:16 -0800
>Message-Id: <41...@mykitchentable.net>
>X-Spam-Flag: YES
>X-Spam-Checker-Version: SpamAssassin 3.0.0 (2004-09-13) on boogey.rootshell.be
>X-Spam-Level: *********
>X-Spam-Status: Yes, score=9.9 required=4.0 tests=BAYES_00,FVGT_TRIPWIRE_BF,
> FVGT_TRIPWIRE_CB,FVGT_TRIPWIRE_DJ,FVGT_TRIPWIRE_FX,FVGT_TRIPWIRE_II,
> FVGT_TRIPWIRE_KB,FVGT_TRIPWIRE_NP,FVGT_TRIPWIRE_PF,FVGT_TRIPWIRE_SB,
> FVGT_TRIPWIRE_SK,FVGT_TRIPWIRE_TK,FVGT_TRIPWIRE_UH,FVGT_TRIPWIRE_XB,
> FVGT_TRIPWIRE_XC,FVGT_TRIPWIRE_XF,LOCAL_OBFU_GENERIC,SARE_HEAD_XBEEN,
> TW_BF,TW_CB,TW_DJ,TW_DR,TW_II,TW_SB,TW_SK,TW_UH,TW_XB,TW_XC,TW_XF
> autolearn=no version=3.0.0
>MIME-Version: 1.0
>Content-Type: multipart/mixed; boundary="----------=_418EB903.359B433A"
>Content-Length: 15125
>Lines: 334
>
>Checker-Version SpamAssassin 3.0.0 (2004-09-13) on boogey.rootshell.be
>Content analysis details: (9.9 points, 4.0 required, autolearn=no)
>
> pts rule name description
>---- ----------------------------------------------------------------
> 0.1 TW_XC BODY: Odd Letter Triples with XC
> 1.8 LOCAL_OBFU_GENERIC BODY: Obfuscated 'GENERIC' in body
> 0.1 TW_BF BODY: Odd Letter Triples with BF
> 0.1 TW_II BODY: Odd Letter Triples with II
> 0.1 TW_UH BODY: Odd Letter Triples with UH
> 0.1 TW_DJ BODY: Odd Letter Triples with DJ
> 0.1 TW_XF BODY: Odd Letter Triples with XF
> 0.1 TW_XB BODY: Odd Letter Triples with XB
> 0.1 TW_SK BODY: Odd Letter Triples with SK
> 0.1 TW_CB BODY: Odd Letter Triples with CB
> 0.1 TW_SB BODY: Odd Letter Triples with SB
> 0.1 TW_DR BODY: Odd Letter Triples with DR
>-2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1%
> [score: 0.0000]
>-0.6 SARE_HEAD_XBEEN Mailng list header found, frequent ham sign
> 0.7 FVGT_TRIPWIRE_CB FVGT_TRIPWIRE_CB
> 0.7 FVGT_TRIPWIRE_PF FVGT_TRIPWIRE_PF
> 0.7 FVGT_TRIPWIRE_UH FVGT_TRIPWIRE_UH
> 0.7 FVGT_TRIPWIRE_II FVGT_TRIPWIRE_II
> 0.7 FVGT_TRIPWIRE_XC FVGT_TRIPWIRE_XC
> 0.7 FVGT_TRIPWIRE_NP FVGT_TRIPWIRE_NP
> 0.7 FVGT_TRIPWIRE_KB FVGT_TRIPWIRE_KB
> 0.7 FVGT_TRIPWIRE_SK FVGT_TRIPWIRE_SK
> 0.7 FVGT_TRIPWIRE_XB FVGT_TRIPWIRE_XB
> 0.7 FVGT_TRIPWIRE_BF FVGT_TRIPWIRE_BF
> 0.7 FVGT_TRIPWIRE_DJ FVGT_TRIPWIRE_DJ
> 0.7 FVGT_TRIPWIRE_FX FVGT_TRIPWIRE_FX
> 0.7 FVGT_TRIPWIRE_SB FVGT_TRIPWIRE_SB
> 0.7 FVGT_TRIPWIRE_XF FVGT_TRIPWIRE_XF
> 0.7 FVGT_TRIPWIRE_TK FVGT_TRIPWIRE_TK
>
>
>
>Received: from mx2.freebsd.org (mx2.freebsd.org [216.136.204.119])
> by boogey.rootshell.be (Postfix) with ESMTP id 4A1002D55F
> for <ha...@rootshell.be>; Mon, 8 Nov 2004 01:08:31 +0100 (CET)
>Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18])
> by mx2.freebsd.org (Postfix) with ESMTP
> id 15C6257BA6; Mon, 8 Nov 2004 00:08:19 +0000 (GMT)
> (envelope-from owner-freebsd-questions@freebsd.org)
>Received: from hub.freebsd.org (localhost [127.0.0.1])
> by hub.freebsd.org (Postfix) with ESMTP
> id 7CE5616A4EA; Mon, 8 Nov 2004 00:08:17 +0000 (GMT)
>Delivered-To: freebsd-questions@freebsd.org
>Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
> by hub.freebsd.org (Postfix) with ESMTP id 335AB16A4CE
> for <fr...@freebsd.org>;
> Mon, 8 Nov 2004 00:08:11 +0000 (GMT)
>Received: from relay04.roc.ny.frontiernet.net (relay04.roc.ny.frontiernet.net
> [66.133.131.37])
> by mx1.FreeBSD.org (Postfix) with ESMTP id A005D43D48
> for <fr...@freebsd.org>;
> Mon, 8 Nov 2004 00:08:10 +0000 (GMT)
> (envelope-from drew@mykitchentable.net)
>Received: from filter02.roc.ny.frontiernet.net
> (filter02.roc.ny.frontiernet.net [66.133.131.177])
> by relay04.roc.ny.frontiernet.net (Postfix) with ESMTP id 262D110285
> for <fr...@freebsd.org>;
> Mon, 8 Nov 2004 00:08:10 +0000 (UTC)
>Received: from relay04.roc.ny.frontiernet.net ([66.133.131.37])
> [66.133.131.177]) (amavisd-new, port 10024)
> with LMTP id 14623-07-8 for <fr...@freebsd.org>;
> Mon, 8 Nov 2004 00:08:10 +0000 (UTC)
>Received: from blacklamb.mykitchentable.net
> (67-137-46-138.dsl2.elk.ca.frontiernet.net [67.137.46.138])
> by relay04.roc.ny.frontiernet.net (Postfix) with ESMTP id 1AD6C101A9
> for <fr...@freebsd.org>;
> Mon, 8 Nov 2004 00:08:08 +0000 (UTC)
>Received: from [192.168.1.25] (lugalong.mykitchentable.net [192.168.1.25])
> (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
> (No client certificate requested)
> by blacklamb.mykitchentable.net (Postfix) with ESMTP id 298EB3BF356
> for <fr...@freebsd.org>;
> Sun, 7 Nov 2004 16:08:06 -0800 (PST)
>Message-ID: <41...@mykitchentable.net>
>Date: Sun, 07 Nov 2004 16:08:16 -0800
>From: Drew Tomlinson <dr...@mykitchentable.net>
>User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913)
>X-Accept-Language: en-us, en
>MIME-Version: 1.0
>To: FreeBSD Questions <fr...@freebsd.org>
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>Content-Transfer-Encoding: 7bit
>X-Virus-Scanned: by amavisd-new-20040701 (2.0) (Debian) at
> filter02.roc.ny.frontiernet.net
>Subject: shutdown -r Hangs After Upgrading to 4.10
>X-BeenThere: freebsd-questions@freebsd.org
>X-Mailman-Version: 2.1.1
>Precedence: list
>List-Id: User questions <freebsd-questions.freebsd.org>
>List-Unsubscribe:
><http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
> <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
>List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
>List-Post: <ma...@freebsd.org>
>List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
>List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
> <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
>Sender: owner-freebsd-questions@freebsd.org
>Errors-To: owner-freebsd-questions@freebsd.org
>
>I've been happily using 4.9-RELEASE-p4 since April 2004. Then,
>I decided to upgrade to 4.10-RELEASE-p3 to fix the pthreads problem
>since I added an external tape drive to the QLogic SCSI card
>that was already in my system.
>
>Anyway, after upgrading, I experienced the same shutdown hanging
>symptoms as described in this message:
>
>http://lists.freebsd.org/pipermail/freebsd-current/2003-December/016933.html
>
>
>In reading the thread, it seems there was an infinite loop problem in
>the ahc driver code that was fixed later by Justin Gibbs. So I tried
>upgrading to 4-STABLE to see if the problem was fixed there. But I
>still have the same symptoms.
>
>I also see these "odd" processes in my ps output:
>
>root 34 0.0 0.0 212 40 ?? Is 10:19PM 0:00.00 adjkerntz
>root 20 0.0 0.0 596 48 ?? DLs 10:08PM 0:00.02 vinum
>root 13 0.0 0.0 0 0 ?? DL 10:08PM 0:00.04 vnlru
>root 12 0.0 0.0 0 0 ?? DL 10:08PM 0:01.39 syncer
>root 11 0.0 0.0 0 0 ?? DL 10:08PM 0:00.26 bufdaemon
>root 10 0.0 0.0 0 0 ?? DL 10:08PM 0:00.00 vmdaemon
>root 9 0.0 0.0 0 0 ?? DL 10:08PM 0:00.73
>pagedaemon
>root 8 0.0 0.0 0 0 ?? DL 10:08PM 0:00.00
>aic_recovery1
>root 7 0.0 0.0 0 0 ?? DL 10:08PM 0:00.00
>aic_recovery1
>root 6 0.0 0.0 0 0 ?? DL 10:08PM 0:00.00
>aic_recovery0
>root 5 0.0 0.0 0 0 ?? DL 10:08PM 0:00.00
>aic_recovery0
>root 4 0.0 0.0 0 0 ?? DL 10:08PM 0:00.00 usbtask
>root 3 0.0 0.0 0 0 ?? DL 10:08PM 0:00.00 usb0
>root 2 0.0 0.0 0 0 ?? DL 10:08PM 0:00.00 taskqueue
>root 1 0.0 0.1 552 128 ?? ILs 10:08PM 0:00.01 init
>root 0 0.0 0.0 0 0 ?? DLs 10:08PM 0:00.00 swapper
>
>I find them "odd" because the system was powered off/on at 6:19AM after
>the machine was shutdown at about 10:08PM. (I tried waiting overnight
>to see if it would actually finish it's shutdown.)
>
>And finally, I have one vinum volume that has problems. However after
>the system comes up, I can remove and re-create the volume and all of my
>data is intact.
>
>I'm assuming that if I get the shutdown issue resolved, these other
>problems will heal themselves. I'd appreciate any advice you might have
>on how to get my system running on 4.10. My dmesg output follows.
>Please let me know if there's any other info I can provide.
>
>Thanks,
>
>Drew
>
>-----
>blacklamb# uname -a
>FreeBSD blacklamb.mykitchentable.net 4.10-STABLE FreeBSD 4.10-STABLE #0:
>Sun Oct 31 21:23:11 PST 2004
>tomlinson_dr@blacklamb.mykitchentable.net:/usr/obj/usr/src/sys/BLACKLAMB
>i386
>
>blacklamb# dmesg
>Copyright (c) 1992-2004 The FreeBSD Project.
>Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
> The Regents of the University of California. All rights reserved.
>FreeBSD 4.10-STABLE #0: Sun Oct 31 21:23:11 PST 2004
> tomlinson_dr@blacklamb.mykitchentable.net:/usr/obj/usr/src/sys/BLACKLAMB
>Timecounter "i8254" frequency 1193182 Hz
>CPU: Pentium III/Pentium III Xeon/Celeron (601.37-MHz 686-class CPU)
>Origin = "GenuineIntel" Id = 0x673 Stepping = 3
>
>Features=0x387fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,PN,MMX,FXSR,SSE>
>
>
>real memory = 201261056 (196544K bytes)
>config> # di pcic0
>Invalid command or syntax. Type `?' for help.
>config> # di ata1
>Invalid command or syntax. Type `?' for help.
>config> # di ata0
>Invalid command or syntax. Type `?' for help.
>config> # di aic0
>Invalid command or syntax. Type `?' for help.
>config> # di adv0
>Invalid command or syntax. Type `?' for help.
>config> q
>avail memory = 191930368 (187432K bytes)
>Programming 24 pins in IOAPIC #0
>IOAPIC #0 intpin 2 -> irq 0
>FreeBSD/SMP: Multiprocessor motherboard: 2 CPUs
>cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000
>cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000
>io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000
>Preloaded elf kernel "kernel" at 0xc03bb000.
>Preloaded userconfig_script "/boot/kernel.conf" at 0xc03bb09c.
>Preloaded elf module "ispfw.ko" at 0xc03bb0ec.
>Pentium Pro MTRR support enabled
>md0: Malloc disk
>Using $PIR table, 11 entries at 0xc00fdf10
>npx0: <math processor> on motherboard
>npx0: INT 16 interface
>pcib0: <Intel 82443BX (440 BX) host to PCI bridge> on motherboard
>IOAPIC #0 intpin 19 -> irq 2
>IOAPIC #0 intpin 18 -> irq 5
>IOAPIC #0 intpin 17 -> irq 10
>IOAPIC #0 intpin 16 -> irq 11
>pci0: <PCI bus> on pcib0
>pcib1: <Intel 82443BX (440 BX) PCI-PCI (AGP) bridge> at device 1.0 on pci0
>pci1: <PCI bus> on pcib1
>pci1: <ATI Mach64-GZ graphics accelerator> at 0.0
>isab0: <Intel 82371AB PCI to ISA bridge> at device 4.0 on pci0
>isa0: <ISA bus> on isab0
>atapci0: <Intel PIIX4 ATA33 controller> port 0x1c90-0x1c9f at device 4.1
>on pci0
>ata0: at 0x1f0 irq 14 on atapci0
>ata1: at 0x170 irq 15 on atapci0
>uhci0: <Intel 82371AB/EB (PIIX4) USB controller> port 0x1ca0-0x1cbf irq
>2 at device 4.2 on pci0
>usb0: <Intel 82371AB/EB (PIIX4) USB controller> on uhci0
>usb0: USB revision 1.0
>uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
>uhub0: 2 ports with 2 removable, self powered
>Timecounter "PIIX" frequency 3579545 Hz
>chip1: <Intel 82371AB Power management controller> port 0xe800-0xe80f at
>device 4.3 on pci0
>ahc0: <Adaptec aic7895 Ultra SCSI adapter> port 0x1000-0x10ff mem
>0xfc100000-0xfc100fff irq 5 at device 5.0 on pci0
>ahc0: Using left over BIOS settings
>aic7895C: Ultra Wide Channel A, SCSI Id=7, 32/253 SCBs
>ahc1: <Adaptec aic7895 Ultra SCSI adapter> port 0x1400-0x14ff mem
>0xfc101000-0xfc101fff irq 5 at device 5.1 on pci0
>ahc1: Host Adapter Bios disabled. Using default SCSI device parameters
>aic7895C: Ultra Wide Channel B, SCSI Id=7, 32/253 SCBs
>fxp0: <Intel 82559 Pro/100 Ethernet> port 0x1cc0-0x1cff mem
>0xfc000000-0xfc0fffff,0xfc102000-0xfc102fff irq 2 at device 6.0 on pci0
>fxp0: Ethernet address 00:e0:18:c4:f4:5e
>inphy0: <i82555 10/100 media interface> on miibus0
>inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
>isp0: <Qlogic ISP 1020/1040 PCI SCSI Adapter> port 0x1800-0x18ff mem
>0xfc103000-0xfc103fff irq 10 at device 9.0 on pci0
>fwohci0: <VIA VT6306> port 0x1c00-0x1c7f mem 0xfc104000-0xfc1047ff irq
>11 at device 10.0 on pci0
>fwohci0: OHCI version 1.0 (ROM=1)
>fwohci0: No. of Isochronous channel is 8.
>fwohci0: EUI64 00:40:63:00:00:00:07:ff
>fwohci0: Phy 1394a available S400, 3 ports.
>fwohci0: Link S400, max_rec 2048 bytes.
>firewire0: <IEEE1394(FireWire) bus> on fwohci0
>sbp0: <SBP-2/SCSI over FireWire> on firewire0
>fwe0: <Ethernet over FireWire> on firewire0
>if_fwe0: Fake Ethernet address: 02:40:63:00:07:ff
>fwohci0: Initiate bus reset
>fwohci0: node_id=0xc800ffc1, gen=1, CYCLEMASTER mode
>firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 (me)
>firewire0: bus manager 1 (me)
>pcib2: <DEC 21152 PCI-PCI bridge> at device 12.0 on pci0
>pci2: <PCI bus> on pcib2
>orm0: <Option ROMs> at iomem 0xc0000-0xc7fff,0xc8000-0xcd7ff on isa0
>pmtimer0 on isa0
>fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
>fdc0: FIFO enabled, 8 bytes threshold
>fd0: <1440-KB 3.5" drive> on fdc0 drive 0
>atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
>vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
>sc0: <System console> at flags 0x100 on isa0
>sc0: VGA <16 virtual consoles, flags=0x100>
>sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
>sio0: type 16550A, console
>sio1 at port 0x2f8-0x2ff irq 3 on isa0
>sio1: type 16550A
>ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0
>ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
>lpt0: <Printer> on ppbus0
>lpt0: Interrupt-driven port
>ppi0: <Parallel I/O> on ppbus0
>APIC_IO: Testing 8254 interrupt delivery
>APIC_IO: routing 8254 via IOAPIC #0 intpin 2
>SMP: AP CPU #1 Launched!
>ad0: 76319MB <GENERIC GENERIC> [155061/16/63] at ata0-master UDMA33
>ad1: 76319MB <WDC WD800AB-22CBA0> [155061/16/63] at ata0-slave UDMA33
>acd0: CDROM <HITACHI CDR-8435> at ata1-master PIO4
>Waiting 10 seconds for SCSI devices to settle
>firewire0: New S400 device ID:00d04b0ce0100707
>sa0 at isp0 bus 0 target 6 lun 0
>sa0: <DEC DLT2000 840F> Removable Sequential Access SCSI-2 device
>sa0: 3.300MB/s transfers
>da0 at ahc0 bus 0 target 0 lun 0
>da0: <SEAGATE SX19171W 9D32> Fixed Direct Access SCSI-2 device
>da0: 11.626MB/s transfers (5.813MHz, offset 8, 16bit), Tagged Queueing
>Enabled
>da0: 8683MB (17783112 512 byte sectors: 64H 32S/T 8683C)
>da1 at ahc0 bus 0 target 2 lun 0
>da1: <SEAGATE SX19171W 9D32> Fixed Direct Access SCSI-2 device
>da1: 11.626MB/s transfers (5.813MHz, offset 8, 16bit), Tagged Queueing
>Enabled
>da1: 8683MB (17783112 512 byte sectors: 64H 32S/T 8683C)
>da2 at sbp0 bus 0 target 0 lun 0
>da2: <Oxford 911G 0135> Fixed Simplified Direct Access SCSI-4 device
>da2: 50.000MB/s transfers
>da2: 76351MB (156368016 512 byte sectors: 255H 63S/T 9733C)
>Mounting root from ufs:/dev/da0s1a
>vinum: drive backup is down
>vinum: removing backup.p0.s0
>vinum: backup.p0 is up
>vinum: backup is up
>vinum: removing backup.p0
>vinum: backup is down
>vinum: removing backup
>vinum: drive backup is up
>vinum: backup.p0.s0 is up
>vinum: backup.p0 is up
>vinum: backup is up
>
>_______________________________________________
>freebsd-questions@freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
>
>
>----- End forwarded message -----