Re: spamd-setup in crontab
Thanks for the tips but does anyone know where this problem come from ? Le 14/11/2011 10:13, Manuel Giraud a C)crit : Hi, I've just set up a mail server with 5.0. I have put spamd in front (in default greylisting mode). It works great following the man pages but when I activate the spamd-setup entry in root's crontab, I receive the following error by mail: spamd-setup: ftp: Could not add blacklist uatrapsWriting -: : Illegal seek Broken pipe If i call spamd-setup as root i have no error message. (note: I've used the default /etc/mail/spamd.conf file). How can I sort this out?
wd0 timeout at boot
Hi, I have a Nexcom NSA-1083 network appliance as firewall which I recently upgraded to OpenBSD 5.0 amd64 and am still having some delays during booting because of wd0 timeout. As I was running OpenBSD 4.4 I was told this somehow might disappear in later releases of OpenBSD but unfortunately it didn't. The symptom is that the boot is delayed of about 2-3 minutes while it is waiting on wd0. So at boot it gets stuck here: wd0(pciide0:0:0): timeout type: ata c_bcount: 512 c_skip: 0 pciide0:0:0: bus-master DMA error: missing interrupt, status=0x21 wd0c: device timeout reading fsbn 0 (wd0 bn 0; cn 0 tn 0 sn 0), retrying wd0(pciide0:0:0): timeout type: ata c_bcount: 512 c_skip: 0 pciide0:0:0: bus-master DMA error: missing interrupt, status=0x21 wd0: transfer error, downgrading to PIO mode 4 wd0(pciide0:0:0): using PIO mode 4 wd0c: device timeout reading fsbn 0 (wd0 bn 0; cn 0 tn 0 sn 0), retrying wd0: soft error (corrected) I am using the following compact flash card: wd0 at pciide0 channel 0 drive 0: SILICONSYSTEMS INC 2GB wd0: 1-sector PIO, LBA, 2001MB, 4098528 sectors wd0(pciide0:0:0): using PIO mode 4, DMA mode 2 So I was wondering now if there is a way to avoid this delay at booting? Would replacing the compact flash card with another moderner one fix it? Or maybe does my BIOS need some tweaking? Regards, ML
Re: I want copy pf.conf from FreeBSD 8.2 to OpenBSD 5 and use it
Never thought I would see confucionism on misc@ Confucius say too much. recent Chinese proverb (from fortune(6)) Julf
it(4) hangs kernel on boot
Hello, With recent binary snapshot it(4) driver hang my system on boot. disabling it(4) allows to boot flawlesly and work after boot without problem. Is that my local hardware problem or bug? I want it(4) because it provides me with watchdog. dmesg without it(4) follows: OpenBSD 5.0-current (GENERIC) #106: Sun Nov 13 20:24:41 MST 2011 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC real mem = 2146369536 (2046MB) avail mem = 2075189248 (1979MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.3 @ 0xf (65 entries) bios0: vendor Phoenix Technologies, LTD version ASUS K8N4-E SE ACPI BIOS Revision 0110 date 05/23/2006 bios0: ASUSTeK Computer INC. K8N4-E SE acpi at bios0 not configured mpbios0 at bios0: Intel MP Specification 1.4 cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD Athlon(tm) 64 Processor 3000+, 2010.56 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 16-way L2 cache cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: AMD erratum 89 present, BIOS upgrade may be required cpu0: apic clock running at 201MHz mpbios0: bus 0 is type PCI mpbios0: bus 1 is type PCI mpbios0: bus 2 is type PCI mpbios0: bus 3 is type PCI mpbios0: bus 4 is type PCI mpbios0: bus 5 is type PCI mpbios0: bus 6 is type ISA ioapic0 at mainbus0: apid 2 pa 0xfec0, version 11, 24 pins pci0 at mainbus0 bus 0 NVIDIA nForce4 DDR rev 0xa3 at pci0 dev 0 function 0 not configured pcib0 at pci0 dev 1 function 0 NVIDIA nForce4 ISA rev 0xa3 nviic0 at pci0 dev 1 function 1 NVIDIA nForce4 SMBus rev 0xa2 iic0 at nviic0 spdmem0 at iic0 addr 0x50: 1GB DDR SDRAM non-parity PC3200CL3.0 spdmem1 at iic0 addr 0x51: 1GB DDR SDRAM non-parity PC3200CL3.0 iic1 at nviic0 ohci0 at pci0 dev 2 function 0 NVIDIA nForce4 USB rev 0xa2: apic 2 int 11, version 1.0, legacy support ehci0 at pci0 dev 2 function 1 NVIDIA nForce4 USB rev 0xa3: apic 2 int 5 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 NVIDIA EHCI root hub rev 2.00/1.00 addr 1 auich0 at pci0 dev 4 function 0 NVIDIA nForce4 AC97 rev 0xa2: apic 2 int 5, nForce4 AC97 ac97: codec id 0x414c4790 (Avance Logic ALC850 rev 0) audio0 at auich0 pciide0 at pci0 dev 6 function 0 NVIDIA nForce4 IDE rev 0xf2: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility wd0 at pciide0 channel 0 drive 0: ST380011A wd0: 16-sector PIO, LBA48, 76319MB, 156301488 sectors wd1 at pciide0 channel 0 drive 1: ST340810A wd1: 16-sector PIO, LBA, 38166MB, 78165360 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5 wd1(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 5 atapiscsi0 at pciide0 channel 1 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: _NEC, DVD_RW ND-3520A, 1.04 ATAPI 5/cdrom removable cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2 pciide1 at pci0 dev 7 function 0 NVIDIA nForce4 SATA rev 0xf3: DMA pciide1: using apic 2 int 5 for native-PCI interrupt pciide2 at pci0 dev 8 function 0 NVIDIA nForce4 SATA rev 0xf3: DMA pciide2: using apic 2 int 11 for native-PCI interrupt ppb0 at pci0 dev 9 function 0 NVIDIA nForce4 PCI-PCI rev 0xa2 pci1 at ppb0 bus 5 vr0 at pci1 dev 7 function 0 VIA VT6105 RhineIII rev 0x8b: apic 2 int 3, address 00:1c:f0:9e:51:b9 ukphy0 at vr0 phy 1: Generic IEEE 802.3u media interface, rev. 9: OUI 0x004063, model 0x0034 nfe0 at pci0 dev 10 function 0 NVIDIA CK804 LAN rev 0xa3: apic 2 int 3, address 00:17:31:b6:d9:c4 atphy0 at nfe0 phy 0: F1 10/100/1000 PHY, rev. 6 ppb1 at pci0 dev 11 function 0 NVIDIA nForce4 PCIE rev 0xa3 pci2 at ppb1 bus 4 ppb2 at pci0 dev 12 function 0 NVIDIA nForce4 PCIE rev 0xa3 pci3 at ppb2 bus 3 ppb3 at pci0 dev 13 function 0 NVIDIA nForce4 PCIE rev 0xa3 pci4 at ppb3 bus 2 ppb4 at pci0 dev 14 function 0 NVIDIA nForce4 PCIE rev 0xa3 pci5 at ppb4 bus 1 vga1 at pci5 dev 0 function 0 vendor NVIDIA, unknown product 0x0a20 rev 0xa2 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) azalia0 at pci5 dev 0 function 1 vendor NVIDIA, unknown product 0x0be2 rev 0xa1: apic 2 int 11 azalia0: no supported codecs pchb0 at pci0 dev 24 function 0 AMD AMD64 0Fh HyperTransport rev 0x00 pchb1 at pci0 dev 24 function 1 AMD AMD64 0Fh Address Map rev 0x00 pchb2 at pci0 dev 24 function 2 AMD AMD64 0Fh DRAM Cfg rev 0x00 kate0 at pci0 dev 24 function 3 AMD AMD64 0Fh Misc Cfg rev 0x00 isa0 at pcib0 isadma0 at isa0 com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 mpu0 at isa0 port 0x330/2: generic MPU-401 compatible midi0 at mpu0: MPU-401 MIDI UART pcppi0 at isa0 port 0x61 spkr0 at pcppi0 lpt0 at isa0 port 0x378/4
Taller Intensivo de Finanzas Directivas, 23 de Noviembre.
290205 [IMAGE] Pms de Mixico prestigiada firma de Capacitacisn presenta: Seminario Intensivo de Finanzas Directivas 23 de Noviembre, Ciudad de Mixico. Promociones especiales por cierre de aqo. Experto consultor Lic. Miguel Bustos Obtenga las herramientas necesarias para alcanzar un sptimo desempeqo en su funcisn. Empresa Registrada ante la STPS Smguenos en Twitter@pmscapacitacion o bien en Facebook PMS de Mixico. !Solicite Mayores Informes! Por favor responda este e-mail con los datos siguientes. Empresa: Nombre: Telifono: Email: Nzmero de Interesados: En breve recibira la informacisn completa de este inigualable evento. Comunmquese a los telifonos y con gusto uno de nuestros ejecutivos le atendera. Telifonos: (0133) 8851-2365, (0133) 8851-2741. 10 lmneas a su servicio. Copyright (C) 2011, PMS Capacitacisn Efectiva de Mixico S.C. Derechos Reservados. PMS de Mixico, El logo de PMS de Mixico son marcas registradas. ADVERTENCIA PMS de Mixico no cuenta con alianzas estratigicas de ningzn tipo dentro de la Republica Mexicana. NO SE DEJE ENGAQAR - DIGA NO A LA PIRATERIA. Todos los logotipos, marcas comerciales e imagenes son propiedad de sus respectivas corporaciones y se utilizan con fines informativos solamente. Este Mensaje ha sido enviado a misc@openbsd.org como usuario de Pms de Mixico o bien un usuario le refiris para recibir este boletmn. Como usuario de Pms de Mixico, en este acto autoriza de manera expresa que Pms de Mixico le puede contactar vma correo electrsnico u otros medios. Si usted ha recibido este mensaje por error, haga caso omiso de el y reporte su cuenta respondiendo este correo con el subject BAJADIRECTIVA Unsubscribe to this mailing list, reply a blank message with the subject UNSUBSCRIBE BAJADIRECTIVA Tenga en cuenta que la gestisn de nuestras bases de datos es de suma importancia y no es intencisn de la empresa la inconformidad del receptor. [demime 1.01d removed an attachment of type image/jpeg which had a name of finanzas directivas.jpg]
Re: wd0 timeout at boot
On 11/15/11 04:45, ML mail wrote: Hi, I have a Nexcom NSA-1083 network appliance as firewall which I recently upgraded to OpenBSD 5.0 amd64 and am still having some delays during booting because of wd0 timeout. As I was running OpenBSD 4.4 I was told this somehow might disappear in later releases of OpenBSD but unfortunately it didn't. The symptom is that the boot is delayed of about 2-3 minutes while it is waiting on wd0. So at boot it gets stuck here: wd0(pciide0:0:0): timeout type: ata c_bcount: 512 c_skip: 0 pciide0:0:0: bus-master DMA error: missing interrupt, status=0x21 wd0c: device timeout reading fsbn 0 (wd0 bn 0; cn 0 tn 0 sn 0), retrying wd0(pciide0:0:0): timeout type: ata ... [ note: no useful dmesg was snipped in this editing. :-/ ] ... So I was wondering now if there is a way to avoid this delay at booting? Would replacing the compact flash card with another moderner one fix it? Or maybe does my BIOS need some tweaking? Regards, ML Does this work for you? http://www.openbsd.org/faq/faq12.html#i386flash Certainly not a proper fix, but a way to avoid it... Nick.
Re: snort and pf - pflog vs if
* Henning Brauer lists-open...@bsws.de [2011-11-14 21:27]: while this is all correct, let me try to pahse it in a way that i think is clearer. the bpf hooks (aka where bpf grabs the packets) are outside pf, i. e. inbound packets hit pf before bpf and outgoing pf ^^ sigh. let me try again. inbound packets hit bpf before pf and outgoing pf before bpf. -- Henning Brauer, h...@bsws.de, henn...@openbsd.org BS Web Services, http://bsws.de, Full-Service ISP Secure Hosting, Mail and DNS Services. Dedicated Servers, Root to Fully Managed Henning Brauer Consulting, http://henningbrauer.com/
Re: wd0 timeout at boot
On 2011-11-15, Nick Holland n...@holland-consulting.net wrote: Does this work for you? http://www.openbsd.org/faq/faq12.html#i386flash Certainly not a proper fix, but a way to avoid it... Easier than soldering the missing line though..
Re: intermittent 5.0/amd64 kernel/X hangs on Tinkpad T60
In an earlier message which apparently didn't make it to the mailing list due to being oversized, I wrote I've just installed 5.0/amd64 (from the CD set) on a Lenovo Thinkpad T60 laptop (dmesg below). I'm running GENERIC.mp. I will probably move to -stable soon, but right now I'm running -release. X autoconfigures and works nicely (1680x1050 pixels, /var/log/Xorg.0.log below), *but* occasionally it hangs. :( :( [[...]] I had 3 more hangs yesterday and 2 more today, the latter both happening within a few minutes of (re)starting X. I've gathered some further information about what's wrong. I'll give a dmesg and /var/log/Xorg.0.log (again) below since the previous ones didn't make it to the list. The basic problem symptoms are that the machine hangs. Most of the times this has happened, the machine has been close to idle, with very low disk/network traffic, no usb devices connected, just me typing in an xterm. When in the hung state: * The screen image stays static. * xclock and xmeter stop updating. * Fn-PgUp DOES work to turn the ThinkLight on/off * If I unplug/plug the AC power I DO get the usual 2-tone beep-bop sound. * The speaker-volume up/down/mute buttons DO work to adjust the volume of that sound. * There's no response (no movement or change of the X cursor) to the touchpad, touchpad buttons, or touchpoint nipple. * There's no response to any other keyboard input. In particular - There's no response to Fn-Home/Fn-End (which should ajust the screen brightness). - There's no response to Ctrl/Alt/Backspace (which should kill the X server) - There's no response to Ctrl/Alt/Delete (which should do a clean OpenBSD halt) I ran memtest86+ (from ports) overnight last night, and it didn't find anything wrong in I think 6 or 8 full passes. Because some Fn-Key operations still work when the machine is hung, I infer that the CPU is still running. Since memtest86+ didn't find any hardware problems, and the machine (so far) never crashes when X is NOT running, I infer (speculate? hope?) that my problem is probably with X, not with the kernel or hardware. I now have an sshd running (I'm currently rsync-ing /home to the spare laptop from which I'm writing this message), so if/when the next hang happens, I can try ssh-ing into the machine to see if the kernel is still alive. In the meantime, some questions: * At the moment I do NOT have a /etc/xorg.conf -- I let X autoconfigure everything. I need an X server that's reliable, but I don't need high performance graphics. Would it be useful to force use of a more generic video driver instead of the fancier radeon one? If so, what's the best way to do this? * Is there extra logging available in the X server which would be useful in tracking down what's wrong? If so, should I mount root and/or var (which I normally mount softdep,noatime) synchronous so more info makes it to disk before a crash/hang? * If I'm able to ssh into the machine when X is hung, what information should I try to gather to help diagnose the problem? --- begin dmesg --- OpenBSD 5.0 (GENERIC.MP) #63: Wed Aug 17 10:14:30 MDT 2011 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 3218931712 (3069MB) avail mem = 3119185920 (2974MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe0010 (68 entries) bios0: vendor LENOVO version 7IET23WW (1.04 ) date 12/27/2006 bios0: LENOVO 87424GU acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT ECDT TCPA APIC MCFG HPET SLIC BOOT SSDT SSDT SSDT SSDT acpi0: wakeup devices LID_(S3) SLPB(S3) LURT(S3) DURT(S3) EXP0(S4) EXP1(S4) EXP2(S4) EXP3(S4) PCI1(S4) USB0(S3) USB1(S3) USB2(S3) USB7(S3) HDEF(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpiec0 at acpi0 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz, 1995.28 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG cpu0: 4MB 64b/line 16-way L2 cache cpu0: apic clock running at 166MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz, 1995.00 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG cpu1: 4MB 64b/line 16-way L2 cache ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 2, remapped to apid 1 acpimcfg0 at acpi0 addr 0xf000, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (AGP_) acpiprt2 at acpi0: bus 2 (EXP0) acpiprt3 at acpi0: bus 3 (EXP1) acpiprt4 at acpi0: bus 4 (EXP2) acpiprt5 at acpi0: bus 12 (EXP3) acpiprt6 at acpi0: bus 21 (PCI1) acpicpu0 at acpi0: C3, C2, C1, PSS acpicpu1 at acpi0:
Re: xenocara build fails on vax
On 11/10/2011 09:13 PM, Maurice Janssen wrote: On 11/10/2011 10:51 AM, Matthieu Herrb wrote: On Wed, Nov 9, 2011 at 7:02 PM, Maurice Janssenmaur...@z74.net wrote: Hi, I'm having some trouble doing a build of xenocara on a vaxstation under 5.0-stable. I know it's not needed because there are no patches for xenocara yet for 5.0-stable, but it bugs me that the build fails consistently. There is a know problem with OpenBSD's pkg-config implementation, which shuffles the order of computed libraries dependencies differently than it used to. It needs to be fixed. In the mean time you can use the pkg-config from 4.9 for that. Thanks, Matthieu. I will give it a try and report back, probably after the weekend. As expected, with pkg-config from 4.9 it worked fine. Thanks, Maurice
Re: spamd-setup in crontab
On 11/14/2011 06:28 AM, James J. Lippard wrote: I had the same problem, which I worked around by changing my spamd.conf to use a local file instead of FTP, and downloading the traplist.gz file in my daily.local. That is, my spamd.conf now looks like this: uatraps:\ :black:\ :msg=Your address %A has sent mail to a ualberta.ca spamtrap\n\ within the last 24 hours:\ :method=file:\ :file=/etc/mail/traplist.gz: And my daily.local now has this: echo Getting traplist.gz. /usr/bin/ftp -o /etc/mail/traplist.gz http://www.openbsd.org/spamd/traplist.gz I question the wisdom of identifying the source of your trapping info. It outs ualberta.ca as a trap. Spammers who actually read (I know most don't) reply messages will know to black list ualberta. Those with infected machines who somehow might get see the message need only know their machine is compromised. Knowing who trapped their spam does not enable the owner of the compromised machine to do any thing they wouldn't do anyhow. The still need to clean up their machine. Regards, Ray
Re: spamd-setup in crontab
On 2011-11-15 20.55, Raymond Lillard wrote: On 11/14/2011 06:28 AM, James J. Lippard wrote: That is, my spamd.conf now looks like this: uatraps:\ :black:\ :msg=Your address %A has sent mail to a ualberta.ca spamtrap\n\ within the last 24 hours:\ :method=file:\ :file=/etc/mail/traplist.gz: I question the wisdom of identifying the source of your trapping info. It outs ualberta.ca as a trap. No, it doesn't. It might out University of Alberta as an organization that fights spam but there is nothing that says that the *domain* ualberta.ca itself contains any of the spam trap addresses. Spammers who actually read (I know most don't) reply messages will know to black list ualberta. Those with infected machines who somehow might get see the message need only know their machine is compromised. Spammers usually never get to see those messages, as they operate through compromised mail servers or pc:s and most likely use fake From: addresses anyway. Knowing who trapped their spam does not enable the owner of the compromised machine to do any thing they wouldn't do anyhow. The still need to clean up their machine. They won't get the messages either... Regards, /Benny -- internetlabbet.se / work: +46 8 551 124 80 / Words must Benny Lofgren/ mobile: +46 70 718 11 90 / be weighed, / fax:+46 8 551 124 89/not counted. /email: benny -at- internetlabbet.se
Re: wd0 timeout at boot
Hi Nick, Well it might be just a workaround but thanks to this fix my firewall now boots smoothly without any timeout and no more error messages. I guess then that it is really related to the compact flash card itself. Regards, ML - Original Message - From: Nick Holland n...@holland-consulting.net To: misc@openbsd.org Cc: Sent: Tuesday, November 15, 2011 1:11 PM Subject: Re: wd0 timeout at boot On 11/15/11 04:45, ML mail wrote: Hi, I have a Nexcom NSA-1083 network appliance as firewall which I recently upgraded to OpenBSD 5.0 amd64 and am still having some delays during booting because of wd0 timeout. As I was running OpenBSD 4.4 I was told this somehow might disappear in later releases of OpenBSD but unfortunately it didn't. The symptom is that the boot is delayed of about 2-3 minutes while it is waiting on wd0. So at boot it gets stuck here: wd0(pciide0:0:0): timeout type: ata c_bcount: 512 c_skip: 0 pciide0:0:0: bus-master DMA error: missing interrupt, status=0x21 wd0c: device timeout reading fsbn 0 (wd0 bn 0; cn 0 tn 0 sn 0), retrying wd0(pciide0:0:0): timeout type: ata ... [ note: no useful dmesg was snipped in this editing. :-/ ] ... So I was wondering now if there is a way to avoid this delay at booting? Would replacing the compact flash card with another moderner one fix it? Or maybe does my BIOS need some tweaking? Regards, ML Does this work for you? http://www.openbsd.org/faq/faq12.html#i386flash Certainly not a proper fix, but a way to avoid it... Nick.
Re: spamd-setup in crontab
On 2011-11-15, Raymond Lillard r...@sonic.net wrote: I question the wisdom of identifying the source of your trapping info. It outs ualberta.ca as a trap. This is fine as far as I'm concerned. If it means the smarter spammers avoid sending to ualberta.ca as a result, that is good for UofA.
anything similar to auditd for openbsd
I have auditd configured on a number of linux servers and I'm trying to find something similar for OpenBSD. Any recommendations? Some of the things I'm looking to log: exec, system-wide read,write,move,delete,etc on selected files read,write,move,delete,etc of /etc Thanks.
Re: terminal descriptions for AMD/Intel consoles
Yeah it's on my todo list :-). On Mon, Nov 14, 2011 at 10:58:10AM +0400, Alexei Malinin wrote: Nicholas Marriott wrote: ... I at least would be pretty reluctant to include full terminfo entries as local changes in OpnBSD. If possible try to get them upstream. Hello, Nicholas. Thomas E. Dickey recently added pccon terminal descriptions to ncurses-current (please see below). Will you update termtypes.master with pccon entries? -- Alexei Malinin Original Message Subject: ncurses-5.9-2012.patch.gz Date: Sat, 12 Nov 2011 21:55:49 -0500 From: Thomas Dickey dic...@his.com Reply-To: dic...@his.com To: Ncurses Mailing List bug-ncur...@gnu.org ncurses 5.9 - patch 2012 - Thomas E. Dickey -- Ncurses 5.9 is at ftp.gnu.org:/pub/gnu Patches for ncurses 5.9 are in the subdirectory ftp://invisible-island.net/ncurses/5.9 -- ftp://invisible-island.net/ncurses/5.9/ncurses-5.9-2012.patch.gz patch by Thomas E. Dickey dic...@invisible-island.net created Sun Nov 13 02:51:43 UTC 2011 -- Ada95/aclocal.m4 | 44 Ada95/configure | 963 +++--- NEWS | 26 aclocal.m4| 44 configure | 2653 dist.mk |4 misc/Makefile.in |4 misc/terminfo.src | 57 + progs/capconvert | 24 test/aclocal.m4 | 12 test/configure| 2627 --- 11 files changed, 3645 insertions(+), 2813 deletions(-) -- 2012 + add pccon entries for OpenBSD console (Alexei Malinin). + build-fix for OpenBSD 4.9 with gcc 4.2.1, setting _XOPEN_SOURCE to 600 to work around inconsistent ifdef'ing of wcstof between C and C++ header files. + modify capconvert script to accept more than exact match on xterm, e.g., the xterm-* variants, to exclude from the conversion (patch by Robert Millan). + add -lc_r as alternative for -lpthread, allows build of threaded code in older FreeBSD machines. + build-fix for MirBSD, which fails when either _XOPEN_SOURCE or _POSIX_SOURCE are defined. + fix a typo misc/Makefile.in, used in uninstalling pc-files. -- Thomas E. Dickey dic...@invisible-island.net http://invisible-island.net ftp://invisible-island.net
Support for LSI MegaRAID 9240?
I am trying to install OpenBSD 5.0 on a SuperMicro system that includes LSI MegaRAID 9240. When it gets to the point of trying to configure the disk partitions it says there are no drives. I assume this is because the standard driver set is not compatible with the RAID controller. Is there any way I can overcome this? Thanks for any assistance. Alan
OpenSMTPd and Monit.
Hi, I'm running a mailserver with smtpd (on OpenBSD) for a small group of folks and get some (very occasional) crashes - usually just corrupted sessions. No big deal, a restart of smtpd is all that it takes. I'm trying to create a Monit (v 4.10.1) recipe that will automatically restart the smtpd process for me, but it just doesn't work. I found the recipe below on a Linux list for monitoring services that don't write a pidfile. -recipe is currently check host localhost with address www.xxx.yyy.zzz start program = /usr/libexec/smtpd -f /etc/mail/smtpd.conf stop program = pkill smtpd if failed host www.xxx.yyy.zzz port 25 type tcp protocol smtp then restart -- Is anyone here using monit to successfully restart smtpd? Any info appreciated. :-) Sarah -- Go out on a limb. Thats where the fruit is - Jimmy Carter
Re: Laptop hard drive and emergency unload
At the risk of replying to a months-old thread which I was guilty of starting, I want to close it with the following observation. I hope this might be of use to others with newer laptops with SATA-drive and crappy Intel chipsets. Today I installed my newly-arrived OpenBSD 5.0 CD (amd64) on my laptop, which has a newer Intel chipset and SATA drive. Initially I ran into the same click sound on halt problem as I had with 4.9. This time however, I noticed that on shutdown, the disk LED didn't light up, as it does when halting Slackware. I then took a look into my BIOS and changed the SATA MODE setting from AHCI to IDE. Now, when shutting down the laptop in IDE mode, the disk LED lights up - indicating the disk is being commanded to shut off, plus there's no more loud click from the drive's emergency unload. Thanks to everyone who provided some observations and advice on this issue. My laptop is now perfectly happy, running the newest release of OpenBSD. Steve On 11-09-05 02:25 PM, Steve wrote: For the fun of it, I just installed 4.9 (AMD64) on an SD card, booted from the card and mounted one of my Ext3 partitions on the hard disk. I copied a file from the disk to the card to be sure it was active, umounted the hard disk and halted. Not a sound from the disk no click, nothing. On 11-09-05 11:13 AM, Philippe Meunier wrote: Steve wrote: 6.3.6.1 Emergency unload [... ]Emergency unload is intended to be invoked in rare situations. Because this operation is inherently uncontrolled, it is more mechanically stressful than a normal unload. Yes. I have a Thinkpad T43 with a Hitachi Travelstar 5K100 (HTS541060G9AT00) and used to have the same problem: when shutting down the computer, the power would be removed from the hard disk while the heads were still loaded and the disk would then have to perform an emergency unload, which resulted in the disk making a loud click. This was the case for me from (I think) OpenBSD 3.9, when I first installed OpenBSD, up to and including 4.8. A few months ago I upgraded to 4.9 (stable) and since then I can hear the disk normally unloading the heads (a short series of 4-5 muffled clicks in very short succession with a slightly increasing pitch) before powering down, which is much quieter. My disk and I both thank whoever implemented that change :-) On Sep 3, 2011, at 15:41, Steve wrote: Can anyone suggest what I could do to stop this from happening? Well, it depends... You could try to manually sync(8) the disk, do something like atactl wd0 apmset 1 (YMMV) to put the disk into standby power saving mode, which would result in the heads being unloaded after a short time, and then halt(8) the computer. The problem is that, as part of the normal powerdown sequence, OpenBSD writes some logs of the shutdown on the disk (which would then reload its heads) and also syncs the disk (I don't know if that action alone would reload the disk heads or not if there were no actual data to sync to the disk; using sync(8) twice in sequence results in my disk's light blinking twice but whether the second blink actually means anything with regard to the disk's heads is an entirely different question...) You could try to play with halt(8)'s -q and -n options and see what happens, but I wouldn't recommend it... Even if you were lucky and it worked, it would be an annoyance to do that every time and it'd be very easy to make a mistake and lose data. You could write scripts to automate the process but you'd be on your own if something went wrong... You could also try the following: - put the root partition, /var/log, and everything else required for a normal shutdown, on a USB stick and boot from that - have all the other stuff (/home, /usr/local, etc) on your disk - before shutting down, manually unmount all the partitions that are on the disk (forcing the unmount if necessary), use atactl to put the disk in a low-power mode that results in the heads being unloaded, then shutdown the computer as usual. Slightly better than the above, but again it'd be annoying to do and it'd be easy to make a mistake... With all that being said, I happily used OpenBSD on my laptop for about five years with my hard disk doing an emergency unload on every shutdown, and never had any problem. It's up to you to decide whether you can sleep at night knowing that your disk goes through a very small number of mechanically stressful events every day. 2 emergency unloads supported by your disk at a minimum (or so Hitachi says...) / 5 shutdowns a day (say) = about 11 years... So it might be an acceptable solution to you until time (and if...) an OpenBSD developer decides to fix your problem. You have backups anyway, right? :-) Philippe
Re: OpenSMTPd and Monit.
Hi, I have no idea about monit but I have a piece of code that might do what you want: http://u.poolp.org/~gilles/projects/procstated/ However that's just a hack, the proper fix is to provide us with the output from 'smtpd -dv' so we can fix the corrupt session bug ;-) Gilles On Tue, Nov 15, 2011 at 10:09:43PM -0500, Sarah Caswell wrote: Hi, I'm running a mailserver with smtpd (on OpenBSD) for a small group of folks and get some (very occasional) crashes - usually just corrupted sessions. No big deal, a restart of smtpd is all that it takes. I'm trying to create a Monit (v 4.10.1) recipe that will automatically restart the smtpd process for me, but it just doesn't work. I found the recipe below on a Linux list for monitoring services that don't write a pidfile. -recipe is currently check host localhost with address www.xxx.yyy.zzz start program = /usr/libexec/smtpd -f /etc/mail/smtpd.conf stop program = pkill smtpd if failed host www.xxx.yyy.zzz port 25 type tcp protocol smtp then restart -- Is anyone here using monit to successfully restart smtpd? Any info appreciated. :-) Sarah -- Go out on a limb. Thats where the fruit is - Jimmy Carter -- Gilles Chehade http://www.poolp.org@poolpOrg
