Re: Carp/Pfsync problem
Kian Mohageri wrote: On 7/31/06, Tim Pushor <[EMAIL PROTECTED]> wrote: Sorry to bump this thread, but I'd really like to know how to troubleshoot something like this. I'd suggest tcpdump'ing at the point when the connection fails, on the pflog(4) interface of both machines, especially the backup which is apparently dropping traffic after failover. Also, you haven't said whether there are any packet filters enabled on the client/server themselves, though I'd assume not. Thanks Kian - you are correct - they are just workstations on either side of the firewall cluster used for testing. They are wide open. I watched the log while attempting the failover. I block log all, so its the first place I look I also watched syslog running with pfctl -x loud, and verified that the state was properly propagated to the backup firewall. Anything else anyone can think of? Thanks, Tim
Re: 3.9 freeze
2006/7/31, diego <[EMAIL PROTECTED]>: Pedro, since I set the "option NKMEMPAGES_MAX=65535" on kernel file, the server doesn't freeze UVM amap128305 10153K 50705K157284K4071891000 0 16,32,64,128,256,512,1024,2048,4096,8192,16384,32768,65536 This server has an uptime 12 days, before the change only alive 3 or 4 days regards,. Doing that changes I can migrate 16GB of messages in mbox format to cyrus without limiting the number of lmtpd processes. I get some "uvm_mapent_alloc: out of static map entries" but the server doesn't freeze. Best regards,
Using dd(1) to duplicate a hard drive
Went back about two years in the MARC archives with the terms 'copy drive' (oddly enough, 'dd' itself wouldn't work), and got plenty of linux examples on Google (that pretty much say what I propose anyway) but no luck... I'm hoping to find a faster way to create an image of one drive (a Samsung MP0402H, 40G notebook, to be specific) onto an identical drive than using: # dd if=/dev/rwd0c of=/dev/rwd1c bs=1m Hardware to be used in the copy is an i586/166, Intel 430VX chipset. I vaguely recall hearing that placing the drives on separate IDE channels would help, but any and all other pointers, cluesticks, and proddings are welcome.
Re: ralink rum(4) driver ?
On Mon, Jul 31, 2006 at 11:40:43AM -0600, Diana Eichert wrote: > First I realize rum(4) is a work in progress, but I've seen some commits > related to the newer Ralink USB wireless chipset using the RT2501. > Reading the rum(4) man page it appears it will support configuring as an > AP. I was thinking about getting one to see how it works. > > Anyone working with these? rx and tx are not yet working, if you want a USB device that can act as an AP now look at the hardware list for ural(4) but be careful as some vendors have replaced chips with the second gen ones rum intends to support and not changed part number.
Re: OpenBSD's own compiler
On 7/31/06, David Leung <[EMAIL PROTECTED]> wrote: I am not a regular GCC user, but my recent experience with it has been quite bitter. Recently I came across a piece of code that only produces correct results with optimization turned on. Yeah, that's not an uncommon result of code that doesn't meet the synchronization requirements of pthreads. My colleague has, by accident, compiled a piece of code we are working on without any optimization, and we notice that the result produced by the unoptimized code is incorrect. As I trace through the code, I found a simple synchronization problem with an external variable being written to by the a number of threads concurrently. Right, so the code caused undefined behavior and the compiler happened to do the desired thing only when optimization was on. Did you not see that same effect with other compilers on that code? ... I'm becoming slightly more cynical about testing any piece of C code with optimization turned on in GCC. What are you testing for? Correct operation of the resulting binary or correctness of the code itself? Note that other cases of undefined behavior (say, violation of C's aliasing rules) are likely to behave 'correctly' when optimization is off. Philip Guenther
Re: OpenBSD's own compiler
> I'm becoming slightly more cynical about testing any piece of C code with > optimization turned on in GCC. And you think this will be different with anyother compiler, you have to be joking. -- Pinski a GCC developer that actually tries to take pride in the recent development of GCC
Re: OpenBSD's own compiler
On Tuesday 01 August 2006 10:08, R. Tyler Ballance wrote: > I really don't want to start a holy war, but I am an idealist, and I > don't think "we" as a community should settle for something like the > GNU Compiler Collection (which I use every day, with about a 50/50 > love-hate relationship). I am not a regular GCC user, but my recent experience with it has been quite bitter. Recently I came across a piece of code that only produces correct results with optimization turned on. My colleague has, by accident, compiled a piece of code we are working on without any optimization, and we notice that the result produced by the unoptimized code is incorrect. As I trace through the code, I found a simple synchronization problem with an external variable being written to by the a number of threads concurrently. The code was hacked up quickly by someone else, and he has been using the -O2 flag all the time when he was writing the code, so the bug has gone undetected for a little while. The bug in our code is quickly fixed, and we're still trying to track down to see why the optimization covered up the bug. I'm becoming slightly more cynical about testing any piece of C code with optimization turned on in GCC.
Re: hard drive problem
RV Tec wrote: Folks, I had two crashes, on two different days, with the same reason: a dying hard drive. Definitively, it is really unpleasant to get caught with my pants down. [there were a few potential comments here, but we'll keep this a family-oriented mailing list! :) (ok, the real truth is I couldn't come up with a punch line that was worthy)] There is a way to test hard drives for possible failures or foresee those errors? Sure: Just expect it. Stuff happens. Just expect it, plan for it, know how you will deal with it, and do so WHEN it happens. Assume it won't happen to you, and you will end up in big trouble eventually. Plan for it, you can make it an annoyance, rather than a disaster. The SMART thing isn't that smart at all. Even after the server crashed twice due faulty harddrive, SMART keeps teeling me everything is OK. Trust your brain, not the machine. Nothing is going to catch all events. I had a drive fail recently where the drive decided to toss a dead short across the power supply...nice, brand new Seagate 500G SATA drive. Casualties: 1 Drive Accusys RAID box (didn't seem to like a dead short) Power supply (agreed with the RAID box, dead shorts suck) Power supply on another P4 machine (which is pissed that Nick felt the need to keep testing this obviously bad drive) 85+G data (which wishes Nick had noticed the incorrect jumper setting on the new Accusys box before giving up and rebuilding the array) Three or four days feeding backup media and uncompressing it. The good news is I anticipated the possibility of such an event, and we had a good backup system in place. Took me several days to fully restore the system, but the entire system was designed to tolerate several days of failure on THIS machine. note: this failure had nothing to do with moving parts. This is a "hypothetical" (ha!) failure mode I've been warning about for years, usually with people rolling their eyes at me and thinking, "There goes Crazy Nick again, warning about things we've never seen". However, after 24 years in the business, I've seen enough to fully believe in Murphy's law..."Anything that can go wrong, will", and the addition: "Some things you didn't imagine could go wrong, will, too". This is a SEAGATE SATA, only 1 year old. I'd expect a longer life of those drives. Am I wrong? You are wrong to expect any particular drive to last any particular life span. You are also probably wrong if you expect a large quantity of drives to actually demonstrate the rated MTBF, but that's another rant. Stuff happens, it has to be part of your plans. Nick.
Re: Gratuitous ARP problem with OpenBSD and MS Cluster Services
On Fri, 2006-07-28 at 14:26 -0700, Clayton Wheeler wrote: > I have a pair of OpenBSD 3.9 firewalls (using pf and carp) attached > to a network with a Windows server cluster on it. The Windows > cluster > moves a shared IP address between nodes using the MAC address of the > actual cluster node, not a common virtual MAC address like pf uses. > When it does this, it sends out gratuitous ARP requests to indicate > that the cluster IP is now associated with a different MAC address. This is an absolutely abhorrent case of software design/engineering. Of course, I would not be surprised if there is an even more abhorrent case of software design/engineering (namely, something lower level in Windows itself) that makes this the only feasible method. Microsoft has no excuse, as CARP is available under the same license as the code they used to help build the original Windows TCP/IP stack. Yes, crontab'ing "arp -ad" as Karsten suggested is a good workaround, but I'd hardly call that a long term fix. -- Shawn K. Quinn
Re: your mail
On Mon, 31 Jul 2006 11:05:06 -0500 Marco Peereboom <[EMAIL PROTECTED]> wrote: > Actually I wrote a very simple piece of code to recover as much as > possible from a hard disk the other day (jordan's disk died with a > lot of code on it and we are still trying to recover it). I'll clean > it up and put it up. How about dd_rescue? Don't know how well it will work on Open though... I think knoppix comes with it. http://www.garloff.de/kurt/linux/ddrescue/
Re: hard drive problem
On Mon, 31 Jul 2006 20:10:23 -0400 Chris <[EMAIL PROTECTED]> wrote: > If all is > lost, you can wipe the disk with BCWipe (www.jetico.com) then test > again with Spinrite. This has recovered several disks for me. Wipe it with dd if=/dev/zero of=/dev/rwd0c count=10, or just take the drive out and beat the crap out of it with a sledge hammer! (Even better if the platters are silicon dioxide rather than aluminum. The industry is moving back to the glass due to perpindicular recording which can't use aluminum as a substrate.) I once used a pick-axe on a drive, the largest piece still intact was about the size of a US quarter. Try getting data off that!
Re: hard drive problem
> There is a way to test hard drives for possible failures or foresee those errors? Try www.Spinrite.com for drive testing and data recovery. If all is lost, you can wipe the disk with BCWipe (www.jetico.com) then test again with Spinrite. This has recovered several disks for me. SMART is close to useless because each vendor implements it differently. Drive temp is about the only common useful stat from SMART.
Re: Carp/Pfsync problem
On 7/31/06, Tim Pushor <[EMAIL PROTECTED]> wrote: > > Sorry to bump this thread, but I'd really like to know how to > troubleshoot something like this. I'd suggest tcpdump'ing at the point when the connection fails, on the pflog(4) interface of both machines, especially the backup which is apparently dropping traffic after failover. Also, you haven't said whether there are any packet filters enabled on the client/server themselves, though I'd assume not. -Kian
SSH connection from UNKNOWN ?
Hi folks. During the last weeks I received some alerts about ssh connections from UNKNOWN. E.g.: Jul 17 08:54:25 piglet sshd[7762]: Did not receive identification string from UNKNOWN Jul 26 05:27:54 piglet sshd[31895]: Did not receive identification string from UNKNOWN After a fast look at the code it seems that getpeername() fails. According to the man page there are several reasons: [... snipp ...] ERRORS On failure, errno is set to one of the following: [EBADF] The argument s is not a valid descriptor. [ENOTSOCK]The argument s is a file, not a socket. [ENOTCONN]The socket is not connected. [ENOBUFS] Insufficient resources were available in the system to per- form the operation. [EFAULT] The name or namelen parameter points to memory not in a valid part of the process address space. [... snipp ...] So some thougts about the reasons that may be a failure: ENOBUFS - Not possible. Although I use 68% of the allocated mbufs I was able to establish new connections from the outside. ENOTCONN and EBADF - As far as I know it is not possible, because the connection log occurs after completing the TCP hand shake. EFAULT- Impossible since I am using OpenBSD :) ENOTSOCK- Connecting to OpenSSH not using a socket? WTF? Is there anyone out there who can help me with this -strange (at least for me)- message. Many thanks in advance, Andreas. P.S.: The system is: OpenBSD piglet.badphish.dyndns.org 3.9 GENERIC#617 i386 running sshd version: OpenSSH_4.3, OpenSSL 0.9.7g 11 Apr 2005 -- Hobbes : Shouldn't we read the instructions? Calvin : Do I look like a sissy?
Disabling dynamic standby mode in EEPROM
My firewall just failed over to the standby firewall (running carp).
They have been running fine for nearly a year, the only thing done to
them was upgrade to 3.9 last may.
The primary firewall is set to preempt but will not take over as master.
Probably a good thing because I think a card (fxp2) has failed.
I saw something in the archive about testing a patch for 3.6 that
writes the eeprom on first boot, but then doesn't again after. This
dmesg is after about 3 reboots in a row, does this mean the firwmware
is fried?
dmesg:
OpenBSD 3.9 (GENERIC) #617: Thu Mar 2 02:26:48 MST 2006
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: AMD Athlon(TM) XP 1600+ ("AuthenticAMD" 686-class, 256KB L2
cache) 1.41 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
cpu0: AMD Powernow: TS
real mem = 1073307648 (1048152K)
avail mem = 972660736 (949864K)
using 4278 buffers containing 53768192 bytes (52508K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(82) BIOS, date 05/07/03, BIOS32 rev. 0 @ 0xf17b0
apm0 at bios0: Power Management spec V1.2 (BIOS mgmt disabled)
apm0: APM power management enable: unrecognized device ID (9)
apm0: APM engage (device 1): power management disabled (1)
apm0: AC on, battery charge unknown
apm0: flags b0102 dobusy 0 doidle 1
pcibios0 at bios0: rev 2.1 @ 0xf/0x1e62
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xf1d90/208 (11 entries)
pcibios0: PCI Interrupt Router at 000:17:0 ("VIA VT82C586 ISA" rev 0x00)
pcibios0: PCI bus #1 is the last bus
bios0: ROM list: 0xc/0xcc00 0xd/0x1800 0xd4000/0x1000 0xd8000/0x1800
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "VIA VT8366 PCI" rev 0x00
ppb0 at pci0 dev 1 function 0 "VIA VT8366 AGP" rev 0x00
pci1 at ppb0 bus 1
vga1 at pci1 dev 0 function 0 "NVIDIA GeForce2 MX" rev 0xb2
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
cmpci0 at pci0 dev 5 function 0 "C-Media Electronics CMI8738/C3DX
Audio" rev 0x10: irq 10
audio0 at cmpci0
uhci0 at pci0 dev 9 function 0 "VIA VT83C572 USB" rev 0x50: irq 5
usb0 at uhci0: USB revision 1.0
uhub0 at usb0
uhub0: VIA UHCI root hub, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1 at pci0 dev 9 function 1 "VIA VT83C572 USB" rev 0x50: irq 11
usb1 at uhci1: USB revision 1.0
uhub1 at usb1
uhub1: VIA UHCI root hub, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
ehci0 at pci0 dev 9 function 2 "VIA VT6202 USB" rev 0x51: irq 10
usb2 at ehci0: USB revision 2.0
uhub2 at usb2
uhub2: VIA EHCI root hub, rev 2.00/1.00, addr 1
uhub2: 4 ports with 4 removable, self powered
fxp0 at pci0 dev 12 function 0 "Intel 8255x" rev 0x0c, i82550: irq 5,
address 00:0e:0c:71:1d:91
inphy0 at fxp0 phy 1: i82555 10/100 PHY, rev. 4
fxp1 at pci0 dev 13 function 0 "Intel 8255x" rev 0x08, i82559: irq 11,
address 00:90:37:34:55:26
inphy1 at fxp1 phy 1: i82555 10/100 PHY, rev. 4
fxp2 at pci0 dev 14 function 0 "Intel 8255x" rev 0x08, i82559: irq 10,
address 00:90:37:34:54:4d
fxp2: Disabling dynamic standby mode in EEPROM, New ID 0x4080, cksum @
0x3f: 0x -> 0xc701
inphy2 at fxp2 phy 1: i82555 10/100 PHY, rev. 4
fxp3 at pci0 dev 15 function 0 "Intel 8255x" rev 0x08, i82559: irq 12,
address 00:90:27:43:4f:b6
inphy3 at fxp3 phy 1: i82555 10/100 PHY, rev. 4
fxp4 at pci0 dev 16 function 0 "Intel 8255x" rev 0x0c, i82550: irq 5,
address 00:0e:0c:74:ef:11
inphy4 at fxp4 phy 1: i82555 10/100 PHY, rev. 4
viapm0 at pci0 dev 17 function 0 "VIA VT8233A ISA" rev 0x00
iic0 at viapm0
"unknown" at iic0 addr 0x18 not configured
asbtm0 at iic0 addr 0x2d
pciide0 at pci0 dev 17 function 1 "VIA VT82C571 IDE" rev 0x06: ATA133,
channel 0 configured to compatibility, channel 1 configured to
compatibility
wd0 at pciide0 channel 0 drive 0:
wd0: 16-sector PIO, LBA, 76319MB, 156301488 sectors
wd0(pciide0:0:0): 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: SCSI0
5/cdrom removable
cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2
uhci2 at pci0 dev 17 function 2 "VIA VT83C572 USB" rev 0x23: irq 9
usb3 at uhci2: USB revision 1.0
uhub3 at usb3
uhub3: VIA UHCI root hub, rev 1.00/1.00, addr 1
uhub3: 2 ports with 2 removable, self powered
uhci3 at pci0 dev 17 function 3 "VIA VT83C572 USB" rev 0x23: irq 9
usb4 at uhci3: USB revision 1.0
uhub4 at usb4
uhub4: VIA UHCI root hub, rev 1.00/1.00, addr 1
uhub4: 2 ports with 2 removable, self powered
isa0 at mainbus0
isadma0 at isa0
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
pcppi0 at isa0 port 0x61
midi0 at pcppi0:
spkr0 at pcppi0
lpt0 at isa0 port 0x378/4 irq 7
npx0 at isa0 port 0xf0/16: using exception 16
pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
pccom1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
Re: OpenBSD's own compiler
Section 4 (commercial distribution) with its beautiful "certain responsibilities" is still there. Section 7 (export control) is still there. On 7/31/06, Ted Unangst <[EMAIL PROTECTED]> wrote: On 7/31/06, AndrC)s <[EMAIL PROTECTED]> wrote: > We should convince both the Free Software Foundation and the Open > Source Initiative that "Lucent Public License Version 1.02" is not a > free software license. Mainly based in Theo's arguments*. > > * [9fans] The new ridiculous license > http://9fans.net/archive/2003/06/270 i don't think 2003 qualifies as new anymore. -- AndrC)s Delfino
Re: OpenBSD's own compiler
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Jul 31, 2006, at 4:32 PM, Andris wrote: We should convince both the Free Software Foundation and the Open Source Initiative that "Lucent Public License Version 1.02" is not a free software license. Mainly based in Theo's arguments*. I most certainly agree, but this raises a question that I think really applies to the GNU Compiler Collection, how "free" should 'we' tolerate? Does an OSI-verified license mean it's free enough for our usage? God I hope not, I've had to work with some of Sun's licensed code, as well as Apple's (public) licensed code, they're both miserable, and absolutely intolerable in my opinion for projects that take pride in the freedom of their code. I highly doubt we would allow for a GPL licensed bit of kernel code (mostly because of the viral aspect of the GPL) but we are ok with depending on a GPL'd compiler collection? While I understand the improbability of this changing anytime soon because, frankly, gcc is the best and only option, but that doesn't mean we should be "ok" with the idea. While the GPLv2 is tolerable, the GPLv3 is looking about as miserable as some of these "corporate" open source licenses. With something as critical to an open source project as the compiler used to build it, the community as a whole, as well as all of the BSD community would greatly benefit from a BSD licensed compiler, even if it is only a C compiler (and hell, why not some BSD licensed binutils ;)) I really don't want to start a holy war, but I am an idealist, and I don't think "we" as a community should settle for something like the GNU Compiler Collection (which I use every day, with about a 50/50 love-hate relationship). Cheers, - -R. Tyler Ballance This paragraph says it all: And come on it says "certain responsibilities". Good god. Are you people dumb to accept such a term in a legal document? It is like "your house mortgage can be considered invalid in certain situations and then we own your house". A BSD future for that compiler is not guaranteed, but I think a free software future is. I don't think Lucent would step back. Maybe they will use a copyleft license, but I think that would be much better than now. * [9fans] The new ridiculous license http://9fans.net/archive/2003/06/270 iD8DBQFEzn9SqO6nEJfroRsRAmzOAJ913NCZ6p0AhQisCEAR506NMGVanACdGJ3G 8F8zSJ5E2mF1suYGC7dMdyg= =n49N -END PGP SIGNATURE-
Re: OpenBSD's own compiler
On 7/31/06, Andris <[EMAIL PROTECTED]> wrote: We should convince both the Free Software Foundation and the Open Source Initiative that "Lucent Public License Version 1.02" is not a free software license. Mainly based in Theo's arguments*. * [9fans] The new ridiculous license http://9fans.net/archive/2003/06/270 i don't think 2003 qualifies as new anymore.
Re: Nagios check_bioctl available
dmesg please On Mon, Jul 31, 2006 at 02:09:21PM -0700, andrew fresh wrote: > On Sun, Jul 30, 2006 at 03:03:26AM +0200, Wijnand Wiersma wrote: > > 2006/7/29, andrew fresh <[EMAIL PROTECTED]>: > > >One thing I ran into is that bioctl needs to run as root to get access > > >to /dev/bio, even for read only access. Is there a way to query bioctl > > >without needing root? > > > > Well, I think you only need the status of the drives and that is > > availlable using sysctl hw.sensors in current (you already mentioned > > sysctl). A monitoring system should not use the capabilities of > > bioctl, it just needs to know the status and report that. > > If that is the case, then this check will become obsolete. That would > be nice! I will have to go put -current on my test box and try it out. > > > As it is, on my 3.9-stable box, the output from sysctl if it is > available does not seem very reliable: > > hw.sensors.29=esm0, Drive 0, drive, online > hw.sensors.30=esm0, Drive 1, drive, online > hw.sensors.31=esm0, Drive 2, drive, unknown > hw.sensors.32=esm0, Drive 3, drive, unknown > hw.sensors.33=esm0, Drive 4, drive, online > hw.sensors.34=esm0, Drive 5, drive, online > hw.sensors.35=esm0, Drive 6, drive, unknown > hw.sensors.36=esm0, Drive 7, drive, unknown > > $ sudo bioctl ami0 > Password: > Volume Status Size Device > ami0 0 Online 8984199168 sd0 RAID1 > 0 Online 8984199168 0:0.0 safte0 > 1 Online 8984199168 0:1.0 safte0 > ami0 1 Online36234592256 sd1 RAID10 > 0 Online18117296128 0:3.0 safte0 ATLAS10K2-TY184JDA40> > 1 Online18117296128 0:4.0 safte0 ATLAS10K2-TY184JDA40> > 2 Online18117296128 0:5.0 safte0 ATLAS10K2-TY184JDA40> > 3 Online18117296128 0:8.0 safte0 ATLAS10K2-TY184JDA40> > ami0 2 Hot spare 8984199168 0:2.0 safte0 > ami0 3 Hot spare 18117296128 0:9.0 safte0 UCHD> > > > The rest of the sensors seem mostly correct though, and there are sure > enough of them! > > $ sysctl hw.sensors | tail -1 > hw.sensors.99=safte0, temp1, OK, temp, 27.78 degC / 82.00 degF > > > Also, on another box that has external disk box connected with ses, I > don't get any status for those disks in sysctl. The disks that are > actually in the server are using safte and those show up in sysctl. I > don't know why, so now I have this check :-) > > > > Now that I think of it, I should add support to the upwatch monitoring > > system too, but I am not that lucky to have hardware to actually test > > it :-) > > If the information is available in sysctl in 4.0, that would be the > check to integrate. > > l8rZ, > -- > andrew - ICQ# 253198 - JID: [EMAIL PROTECTED] > > BOFH excuse of the day: dynamic software linking table corrupted
Re: OpenBSD's own compiler
On Mon, Jul 31, 2006 at 10:35:29AM -0500, R. Tyler Ballance wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > >>I was wondering, would it be a stupid and bad idea, for the > >>OpenBSD team to > >>develope, an OpenBSD C compiler based upon the OpenBSD security > >>knowledge > >>and internal standards regarding the language? > > > >yeah we will just drop everything we do now, quit all our jobs, > >send our families and other sos shopping at the mall in zimbabwe, > >not make a release for two years and produce the best compiler > >ever by then of course everybody will stop using openbsd for > >obvious reasons so we can finally all go drinking beer... > > Jeeez, talk about an overreaction to the suggestion. The GNU Compiler > Collection has been something most people "put up with" as opposed to > "enjoy" using. It's not that far fetched of an idea, remember a spin- Once we wondered about a bug in our Links web browser and we traced it down to a bug in gcc - the preprocessing was generating improper output (empty) when it should have generated something else. Existed only in particular version of GCC that was used at that time. Having a correctness-based approach and bugfree program doesn't help when the compiler is broken and introduces bugs into the code. CL< > off project that the OpenBSD guys are responsible that's become the > most heavily used SSH code on the planet... > > Since nobody else has mentioned TeNDRA project, I might as well: > http://www.tendra.org/ > > If you're interested in a BSD compiler collection, start by helping > them out, it's been dormant (somewhat) but I'm certain it'd just take > a few talented individuals with spare time to really get it going again. > > > Cheers, > > - - -R. Tyler Ballance > Lead Developer, bleep. LLC > http://www.bleepsoft.com > iD8DBQFEziNDqO6nEJfroRsRAisbAJ9QNotFvmY/WDqscfEqaXC5mkSsCwCfcATB > G1z5mX5wkbEz5qPlnzpcQbw= > =1Q3E > -END PGP SIGNATURE-
Re: OpenBSD's own compiler
We should convince both the Free Software Foundation and the Open Source Initiative that "Lucent Public License Version 1.02" is not a free software license. Mainly based in Theo's arguments*. This paragraph says it all: And come on it says "certain responsibilities". Good god. Are you people dumb to accept such a term in a legal document? It is like "your house mortgage can be considered invalid in certain situations and then we own your house". A BSD future for that compiler is not guaranteed, but I think a free software future is. I don't think Lucent would step back. Maybe they will use a copyleft license, but I think that would be much better than now. * [9fans] The new ridiculous license http://9fans.net/archive/2003/06/270
Re: Nagios check_bioctl available
On Sun, Jul 30, 2006 at 03:03:26AM +0200, Wijnand Wiersma wrote: > 2006/7/29, andrew fresh <[EMAIL PROTECTED]>: > >One thing I ran into is that bioctl needs to run as root to get access > >to /dev/bio, even for read only access. Is there a way to query bioctl > >without needing root? > > Well, I think you only need the status of the drives and that is > availlable using sysctl hw.sensors in current (you already mentioned > sysctl). A monitoring system should not use the capabilities of > bioctl, it just needs to know the status and report that. If that is the case, then this check will become obsolete. That would be nice! I will have to go put -current on my test box and try it out. As it is, on my 3.9-stable box, the output from sysctl if it is available does not seem very reliable: hw.sensors.29=esm0, Drive 0, drive, online hw.sensors.30=esm0, Drive 1, drive, online hw.sensors.31=esm0, Drive 2, drive, unknown hw.sensors.32=esm0, Drive 3, drive, unknown hw.sensors.33=esm0, Drive 4, drive, online hw.sensors.34=esm0, Drive 5, drive, online hw.sensors.35=esm0, Drive 6, drive, unknown hw.sensors.36=esm0, Drive 7, drive, unknown $ sudo bioctl ami0 Password: Volume Status Size Device ami0 0 Online 8984199168 sd0 RAID1 0 Online 8984199168 0:0.0 safte0 1 Online 8984199168 0:1.0 safte0 ami0 1 Online36234592256 sd1 RAID10 0 Online18117296128 0:3.0 safte0 1 Online18117296128 0:4.0 safte0 2 Online18117296128 0:5.0 safte0 3 Online18117296128 0:8.0 safte0 ami0 2 Hot spare 8984199168 0:2.0 safte0 ami0 3 Hot spare 18117296128 0:9.0 safte0 The rest of the sensors seem mostly correct though, and there are sure enough of them! $ sysctl hw.sensors | tail -1 hw.sensors.99=safte0, temp1, OK, temp, 27.78 degC / 82.00 degF Also, on another box that has external disk box connected with ses, I don't get any status for those disks in sysctl. The disks that are actually in the server are using safte and those show up in sysctl. I don't know why, so now I have this check :-) > Now that I think of it, I should add support to the upwatch monitoring > system too, but I am not that lucky to have hardware to actually test > it :-) If the information is available in sysctl in 4.0, that would be the check to integrate. l8rZ, -- andrew - ICQ# 253198 - JID: [EMAIL PROTECTED] BOFH excuse of the day: dynamic software linking table corrupted
Re: More to hanging audio
On Mon, Jul 31, 2006 at 11:18:06AM -0400, Jeff Quast wrote: > On 7/31/06, Karel Kulhavy <[EMAIL PROTECTED]> wrote: > >I examined dmesg, there were no late messages. Tried shutting down X > >Windows > >and playing from console. Didn't help. Reboot helped. My dmesg: > > > > Are you willing to install snapshots, upgrade to -current and see if > the bug still exists? File a descriptive bug report? What are you Hardly - XMMS crashes quite often and this problem happened only once. > trying to accomplish here? Are you just whining? I am trying to accomplish that the developers know about a problem and can target it. > > Have you read audioctl(1) ? Played with it? Looked at it? Have you Read, not played. Looked at it. > read auich(4) ? Have you read the caveat? Are you playing 48kHz Yes. Yes. > sampling rates? Have you looked at google? Are you sick of all of I don't know if I have any 48kHz mp3's. > these questions yet? No. CL<
Re: Audio hangs in 3.9
On Mon, Jul 31, 2006 at 11:22:30AM -0400, Jeff Quast wrote: > On 7/31/06, Karel Kulhavy <[EMAIL PROTECTED]> wrote: > >My xmms crashed so I killed it and make sure no more xmms process is > >running > >there. Then I tried XMMS several times again and every time I pressed play > >it hangs. > > For fucks sakes. What does any of this mean? Xmms? Are you whining > about xmms? Thanks for the details fuckface. Glad I could help. No, I am not whining about XMMS. The point is that the kernel gets into a state when the audio doesn't work anymore. Without any audio application running. I would expect the audio in the kernel to continue working after userland app crashes and all running audio processes are cleared out. A userland application should not be able to bring any subsystem in the kernel down. Otherwise it's a DoS vulnerability - one user blocks the audio on multi-user machine in a computer lab and all remotely working people have to stop working, log out, then the machine needs to be rebooted, and then the same user can bring the audio down again and the cycle can continue. DoS attack. CL< > > >Is the audio in OpenBSD kernel hanging or what? > > http://catb.org/~esr/faqs/smart-questions.html#id265155 > see "Grovelling is not a substitute for doing your homework"
Re: Nagios check_bioctl available
On Fri, Jul 28, 2006 at 09:17:28PM -0500, Marco Peereboom wrote: > andrew fresh wrote: > >I have written a perl script that parses the output from bioctl and > >returns it in a format that Nagios can use. > > Sweet :-) Thanks! > >One thing I ran into is that bioctl needs to run as root to get access > >to /dev/bio, even for read only access. Is there a way to query bioctl > >without needing root? > > No! dang! oh well, sudo is a good enough solution then. > >Also, in biovar.h, both a raid volume and a disk can be "Offline". > >However, I am not sure what that means. Currently it is a WARNING, but > >I don't know what status it should be set to. > > If 2 or more physical disks of a RAID 5 are offline a volume will be > marked offline as well. An offline RAID 5 is obviously a critical > event. Hope this makes sense since I am not exactly sure what you are > asking. I will change Offline to be a CRITICAL error. and here is the new version: http://openbsd.somedomain.net/nagios/check_bioctl-1.4.tar.gz However, I guess my question is what would cause a disk to be Offline? There is a separate status for Failed, and I could see the RAID being Offline if too many disks had Failed. Are there any other status that should be different? They seemed to be fairly straight forward, but there may be good arguments for them to be changed. my %Status_Map = ( Online => 'OK', Offline => 'CRITICAL', Degraded=> 'CRITICAL', Failed => 'CRITICAL', Building=> 'WARNING', Rebuild => 'WARNING', 'Hot spare' => 'OK', Unused => 'OK', Scrubbing => 'WARNING', Invalid => 'CRITICAL', ); l8rZ, -- andrew - ICQ# 253198 - JID: [EMAIL PROTECTED] BOFH excuse of the day: Windows 95 undocumented "feature"
Re: OpenBSD's own compiler
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Jul 31, 2006, at 1:32 PM, Rogier Krieger wrote: On 7/31/06, R. Tyler Ballance <[EMAIL PROTECTED]> wrote: Jeeez, talk about an overreaction to the suggestion. [...] It's not that far fetched of an idea Given the times that this question popped up in the archives, Mickey's reaction isn't too surprising. From the past discussions, I gather that a change of compiler would be a massive job, regardless of the compiler changed to. That said, I'll happily admit that I didn't make a time estimate for the job. I don't have any doubts whatsoever about that, GCC has been around almost as long as I have, and I'd still say it's got a lot of work to be done (when compared to proprietary compilers, but it's price tag and open source code still makes it my choice). "OpenSSH is a derivative of the original free ssh 1.2.12 release from Tatu Ylvnen. This version was the last one which was free enough for reuse by our project." Good point, I did forget that OpenSSH wasn't exactly from scratch, as of now there aren't really any decent alternatives to pick up appropriately licensed source code from to start an OpenCC project from (for example). [...] but I'm certain it'd just take a few talented individuals with spare time to really get it [TeNDRA] going again. The above does not include the work done on actually obtaining a compiler desired. Be it from scratch or by working on existing code, I recommend to be careful whose spare time you volunteer. You're the second person to make this allusion that I am some PHB spending other people's time, I was merely making the argument that it only takes a few talented individuals to get a snowball project going that would be capable of picking up speed as more people contributed to it. While it would be a massive undertaking, I still think a project like this would carry merit, and would definitely carry my support (I am absolutely no good with grammars so my support would be more evangelical ;)). Then again, given the amount of time that it would take to make a new _decent_ compiler, I'd say efforts would be best spent bribing some of those Plan9 guys into releasing their compilers under a BSD license ;) Cheers, - -R. Tyler Ballance iD8DBQFEzm0YqO6nEJfroRsRAtpbAJ98XWuKKaHCDKPvCTYnY08zIZs++wCfb3Mf DtQUljINsTRodDBp518CbLI= =E3jD -END PGP SIGNATURE-
OpenBSD at DefCon
Is anyone on misc going to be at DefCon this weekend? If you are, get in touch. Would be nice to have a beer with other users or developers. If this has already been asked and I missed the thread, then flame away.
Re: USB sound device recommendations?
On Sun, Jul 30, 2006 at 10:04:32PM +0200, Matthias Kilian wrote: > Hi, > > has anyone tested the Creative SoundBlaster Live! 24Bit USB on > OpenBSD or can recommend a similar (or better) device? > hi, i've got a m-audio "mobile pre", it sounds really good and is fully supported by openbsd. It's also good for recording. > And for that Creative thing: is the wave table synthesizer really > onboard, or is it just some bogus thing supported by windows drivers > only? > i don't know about the creative thing. Instead of a card with a wavetable, i use an external USB/MIDI sound module (roland xv-2020). It appears as an umidi(4) device and is fully usable on openbsd. -- Alexandre
Re: OpenBSD's own compiler
On 7/31/06, R. Tyler Ballance <[EMAIL PROTECTED]> wrote: Jeeez, talk about an overreaction to the suggestion. [...] It's not that far fetched of an idea Given the times that this question popped up in the archives, Mickey's reaction isn't too surprising. From the past discussions, I gather that a change of compiler would be a massive job, regardless of the compiler changed to. That said, I'll happily admit that I didn't make a time estimate for the job. [...] remember a spin-off project that the OpenBSD guys are responsible that's become the most heavily used SSH code on the planet... Given the History page on OpenSSH.org [1], licensing terms are likely to have been a factor as well. To quote: "OpenSSH is a derivative of the original free ssh 1.2.12 release from Tatu Ylvnen. This version was the last one which was free enough for reuse by our project." [...] but I'm certain it'd just take a few talented individuals with spare time to really get it [TeNDRA] going again. The above does not include the work done on actually obtaining a compiler desired. Be it from scratch or by working on existing code, I recommend to be careful whose spare time you volunteer. Cheers, Rogier References: 1. OpenSSH Project History and Credits http://www.openssh.org/history.html -- If you don't know where you're going, any road will get you there.
Re: openBSD 3.8 window scaling problem: packets dropped on enc0?
Hi, I don't know if you eventually got an answer on this or not, but I got bit by this with my upgrade to 2.6.17.7 on my linux workstation and my pf firewall started blocking connections. Turns out, that pf is not to blame, but a sloppy ruleset (at least in my case). The thing to check for is to make sure that all rules that affect TCP use 'flags S/SA keep state' so that the window scaling negotiation is caught by pf and it won't invalidate perfectly valid packets just because it thinks they are outside of the TCP window. here's the best link I've found: http://mail-index.netbsd.org/tech-net/2006/07/12/.html On 2/10/06, Christoph Leser <[EMAIL PROTECTED]> wrote: scp from linux to linux via an ipsec tunnel between openBSD gateway and lancom 1611+ router fails( hangs) if tcp window scaling is enabled. This is my setup: Redhat Linux ES3 <---> dc0 openBSD IPSEC dc1 < internet -> lancom 1611+ <---> Redhat Linux ES4 RHES3 does scp a.a host:/directory ask for password, and then hangs, given the file is larger that about 1300 bytes. tcpdump on openBSD dc0 and enc0 shows: RHES3 sends SYN with wscale=0, receives SYN with wscale=3 sends and receives some small packets during negotiation sends a first full size packet, which I see on dc0, but not on enc0 and hangs, repeating this first packet. This only happens, when RHES3 is copying data to RHES4. If RHES3 is copying data from RHES4, it works, but very slow. The problem can be worked around by setting net.ipv4.tcp_window_scaling=0 on RHES3, effectively disabling the window scale feature. Is this a known problem? Or possibly caused by some sort of misconfiguration? I will happily provide more details, tcpdumps etc. if you are interested. I found that Stephen Hemminger claims on Linux World Expo Feb. 2005 that openBSD might fail to track state when window scaling is in effect. See http://developer.osdl.org/shemminger/LWE2005_TCP.pdf .
ralink rum(4) driver ?
First I realize rum(4) is a work in progress, but I've seen some commits related to the newer Ralink USB wireless chipset using the RT2501. Reading the rum(4) man page it appears it will support configuring as an AP. I was thinking about getting one to see how it works. Anyone working with these? thanks
Re: OpenBSD's own compiler
On Mon, Jul 31, 2006 at 10:35:29AM -0500, R. Tyler Ballance wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > >>I was wondering, would it be a stupid and bad idea, for the > >>OpenBSD team to > >>develope, an OpenBSD C compiler based upon the OpenBSD security > >>knowledge > >>and internal standards regarding the language? > > > >yeah we will just drop everything we do now, quit all our jobs, > >send our families and other sos shopping at the mall in zimbabwe, > >not make a release for two years and produce the best compiler > >ever by then of course everybody will stop using openbsd for > >obvious reasons so we can finally all go drinking beer... > > Jeeez, talk about an overreaction to the suggestion. The GNU Compiler > Collection has been something most people "put up with" as opposed to > "enjoy" using. It's not that far fetched of an idea, remember a spin- > off project that the OpenBSD guys are responsible that's become the > most heavily used SSH code on the planet... > > Since nobody else has mentioned TeNDRA project, I might as well: > http://www.tendra.org/ > > If you're interested in a BSD compiler collection, start by helping > them out, it's been dormant (somewhat) but I'm certain it'd just take > a few talented individuals with spare time to really get it going again. just god damn try it. come back when you can compile and run a "hello world"... cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: pf: state insert failed: tree_lan_ext
Rickard Dahlstrand wrote: > Darrin Chandler wrote: > >> On Sun, Jul 30, 2006 at 11:11:17PM +0200, Rickard Dahlstrand wrote: >> >> >>> Hi, >>> >>> With the rulesset: >>> nat on sis0 from !(sis0) -> (sis0) >>> rdr on sis0 inet proto udp from any to any port = 12560 -> 192.168.1.10 >>> port 1 >>> rdr on sis0 inet proto udp from any to any port = 12561 -> 192.168.1.10 >>> port 10001 >>> (and pass quick on all if, no keep state) >>> >>> I get these errors when running debug misc: >>> pf: state insert failed: tree_lan_ext lan: 192.168.1.10:1 gwy: >>> xx.xxx.xxx.xx:12560 ext: uu.uu.uu.uu:18358 >>> >>> The udp-stream from 192.168.1.10 gets passed OK, but the incoming stream >>> from uu.uu.uu.uu triggers the above error. >>> >>> Anyone has any idea on why this does occur and if there is any way that >>> I can get it working. >>> >>> Thanks, Rickard. >>> >>> >> Have you tried using nonat to exclude your rdr ports? >> >> > Yes, if I do that it stoppes the outgoing stream as well. > To expand this question a bit, is there a way to instruct nat not to create a bi-directional state. Rickard.
Re:
On Monday 31 July 2006 09:41, you wrote: >The SMART thing isn't that smart at all. Even after the server crashed >twice due faulty harddrive, SMART keeps teeling me everything is OK. I think (someone with more knowledge may correct me if i'm wrontg) SMART communicates with the drive and asks the drive's electronics if anything is wrong. So SMART can only report problems that the drive detects. >This is a SEAGATE SATA, only 1 year old. I'd expect a longer life of > those drives. Am I wrong? Drives are rated with a "mean time before failure". Though the number given is quite high on modern drives, it is still an average. Some percentage of the drives will die in a few months, some will last for 2 years, some for 5 years, etc. Most of the drives produced should last longer than people care to use them. I have a drive at home that has been running for over 8 years continuously (except for moving the computer or power outages). I have had other drives fail a couple months after purchase. >[lengthy error messages removed] I've had many problems with hard drives. The types of errors that you are seeing correspond with errors i have received when i had a bad data cable. I haven't had cable problems with SATA, only parallel ATA. But i also have not used SATA drives very much yet (most of my equipment is old). My experience has been that data cables in PCs are made very cheaply and can spontaneously go bad. More often they go bad after being disturbed; have you had the computer open recently? Occasionally cables are even bad when new. I'd suggest replacing the data cable with a new one or one that is known good and see if you still get the errors. When i've had hard drive problems (especially if they are intermittent) i've usually been able to solve them by getting the highest quality cable i could find and using it instead of whatever i had been using. Replacing a cable (even with a relatively expensive new cable) is also much cheaper than getting a new drive, or paying shipping on a bad drive that is still under warranty. Good luck with your drive! I know that dealing with bad drives and cables can be quite frustrating. -- Dan RamaleyDial Center 118, Drake University Network Programmer/Analyst 2407 Carpenter Ave +1 515 271-4540Des Moines IA 50311 USA
Re: Carp/Pfsync problem
Sorry to bump this thread, but I'd really like to know how to
troubleshoot something like this.
Should this work? Should I expect the firewall to fail over a TCP
session? I'm thinking yes, since it does what its supposed to when
shutting down the active firewall mid-stream, but not when I pull the
plug on one.
Thanks again,
Tim
Tim Pushor wrote:
Hi friends,
I am trying to setup my first firewall w/failover via carp & pfsync. I
have it almost working, but am having a couple issues. I am hoping
someone will be able to help :)
First, before I enabled preemption I almost always had one machine
being master for one of the carp interfaces, and slave for the other
two. It seemed to work, but just looked troublesome. Enabling
preemption seemed to solve this. Does this point to a bigger problem
somewhere?
Second, and what I am really trying to fix - is to have an in progress
TCP session fail over to the second firewall. The connection stalls
and eventually times out when failing over, but attempting to
re-establish after the failover works (through the second firewall).
I've confirmed (at least in my mind) that state updates are being
properly propagated to the second firewall by watching the pfsync
interface, and noting the state via pfctl -s state. I've watched
syslog with pfctl -x loud and didn't see anything.
Any hints on how I can go about troubleshooting this further? I've
included as much info as I can think of. The included PF ruleset is
just a proof of concept - I realize theres quite a bit more to be
done, I'm just trying to get the failover working.
Thanks!,
Tim
BTW If there is any OpenBSD guru in Calgary thats looking for a few
hours of consultancy I'd love to hear from you :)
Details:
Both systems are Dell 850 servers w/added Intel Etherexpress Pro
10/100 cards as the pfsync interface, with a crossover cable between
them. OS is OpenBSD 3.9, GENERIC Kernel.
192.168.1.246
+--+
| Test Workstation |
+--|
|
+| carp1 |+
| 192.168.1.22 |
| |
+| carp2 |+
| 192.168.1.23 |
||
192.168.1.20 bge0||bge0 192.168.1.21
+-+ +-+
| fw1 |-fxp0fxp0-| fw2 |
+-+ +-+
10.0.10.253 bge1||bge1 10.0.10.254
||
---+--- carp0 ---+---
10.0.10.1
|
|
+-+
| Test Server |
+-+
10.0.10.42
(fw1 fxp0 - 192.168.254.253)
(fs2 fxp0 - 192.168.254.254)
fw1:
# cat hostname.bge0
inet 192.168.1.20 255.255.255.0 NONE
# cat hostname.bge1
inet 10.0.10.253 255.255.255.0 NONE
# cat hostname.fxp0
inet 192.168.254.253 255.255.255.0 NONE
# cat hostname.carp0
inet 10.0.10.1 255.255.255.0 10.0.10.255 vhid 1 pass foo1 carpdev bge1
# cat hostname.carp1
inet 192.168.1.22 255.255.255.0 192.168.1.255 vhid 2 pass foo2 carpdev
bge0
# cat hostname.carp2
inet 192.168.1.23 255.255.255.0 192.168.1.255 vhid 3 pass foo3 carpdev
bge0
# cat hostname.pfsync0
up syncif fxp0
# sysctl -a | grep carp
net.inet.carp.allow=1
net.inet.carp.preempt=1
net.inet.carp.log=0
net.inet.carp.arpbalance=0
fw2:
# cat hostname.bge0
inet 192.168.1.21 255.255.255.0 NONE
# cat hostname.bge1
inet 10.0.10.254 255.255.255.0 NONE
# cat hostname.fxp0
inet 192.168.254.254 255.255.255.0 NONE
# cat hostname.carp0
inet 10.0.10.1 255.255.255.0 10.0.10.255 vhid 1 pass foo1 advskew 128
carpdev bge1
# cat hostname.carp1
inet 192.168.1.22 255.255.255.0 192.168.1.255 vhid 2 pass foo2 advskew
128 carpdev bge0
# cat hostname.carp2
192.168.1.23 255.255.255.0 192.168.1.255 vhid 3 pass foo3 advskew 128
carpdev bge0
# cat hostname.pfsync0
up syncif fxp0
# sysctl -a | grep carp
net.inet.carp.allow=1
net.inet.carp.preempt=1
net.inet.carp.log=0
net.inet.carp.arpbalance=0
PF Rules (identical on both machines)
# cat /etc/pf.conf
ext_if="bge0"
int_if="bge1"
pfsync_if="fxp0"
# All interfaces (real + virtual via carp) thought of as external
ext_ifs="{ bge0, carp1, carp2 }"
# Our internal network(s). Used for access rules and NAT
internal_nets="10.0.10.0/24"
# Define NAT source port range (all source ports will be rewritten to use
# this range)
nat_port_range="20001:65535"
# Define virtual carp interface that should be used as NAT source
# (i.e. outbound hide nat will appear to come from this virtual
interface)
nat_carp="carp1"
# real interfaces that have
Re: your mail
Actually I wrote a very simple piece of code to recover as much as possible from a hard disk the other day (jordan's disk died with a lot of code on it and we are still trying to recover it). I'll clean it up and put it up. On Mon, Jul 31, 2006 at 10:41:21AM -0400, RV Tec wrote: > Folks, > > I had two crashes, on two different days, with the same reason: a dying > hard drive. Definitively, it is really unpleasant to get caught with my > pants down. > > There is a way to test hard drives for possible failures or foresee > those errors? > > The SMART thing isn't that smart at all. Even after the server crashed > twice due faulty harddrive, SMART keeps teeling me everything is OK. > > This is a SEAGATE SATA, only 1 year old. I'd expect a longer life of those > drives. Am I wrong? > > Jul 30 13:23:36 home wd0 at pciide1 channel 0 drive 0: > Jul 30 13:23:36 home wd0: 16-sector PIO, LBA48, 76319MB, 156301488 sectors > Jul 30 13:23:36 home wd0(pciide1:0:0): using PIO mode 4, Ultra-DMA mode 5 > > Jul 29 13:53:55 home wd0(pciide1:0:0): timeout > Jul 29 13:53:55 home type: ata > Jul 29 13:53:55 home type: ata > Jul 29 13:53:55 home c_bcount: 16384 > Jul 29 13:53:55 home c_bcount: 16384 > Jul 29 13:53:55 home c_skip: 0 > Jul 29 13:53:55 home c_skip: 0 > Jul 29 13:53:55 home pciide1:0:0: bus-master DMA error: missing interrupt, > status=0x21 > Jul 29 13:53:55 home pciide1:0:0: bus-master DMA error: missing interrupt, > status=0x21 > Jul 29 13:53:55 home wd0f: device timeout reading fsbn 1984192 of > 1984192-1984223 (wd0 bn 30295888; cn 30055 tn 7 sn 7), retrying > Jul 29 13:53:55 home wd0f: device timeout reading fsbn 1984192 of > 1984192-1984223 (wd0 bn 30295888; cn 30055 tn 7 sn 7), retrying > Jul 29 13:53:55 home wd0: soft error (corrected) > Jul 29 13:53:55 home wd0: soft error (corrected) > Jul 29 13:54:05 home wd0(pciide1:0:0): timeout > Jul 29 13:54:05 home wd0(pciide1:0:0): timeout > Jul 29 13:54:05 home type: ata > Jul 29 13:54:05 home type: ata > Jul 29 13:54:05 home c_bcount: 16384 > Jul 29 13:54:05 home c_bcount: 16384 > Jul 29 13:54:05 home c_skip: 0 > Jul 29 13:54:05 home c_skip: 0 > Jul 29 13:54:05 home pciide1:0:0: bus-master DMA error: missing interrupt, > status=0x21 > Jul 29 13:54:05 home pciide1:0:0: bus-master DMA error: missing interrupt, > status=0x21 > Jul 29 13:54:05 home wd0: transfer error, downgrading to Ultra-DMA mode 4 > Jul 29 13:54:05 home wd0: transfer error, downgrading to Ultra-DMA mode 4 > Jul 29 13:54:05 home wd0(pciide1:0:0): using PIO mode 4, Ultra-DMA mode 4 > Jul 29 13:54:05 home wd0(pciide1:0:0): using PIO mode 4, Ultra-DMA mode 4 > Jul 29 13:54:05 home wd0e: device timeout reading fsbn 1113568 of > 1113568-1113599 (wd0 bn 12648112; cn 12547 tn 11 sn 43), retrying > Jul 29 13:54:05 home wd0e: device timeout reading fsbn 1113568 of > 1113568-1113599 (wd0 bn 12648112; cn 12547 tn 11 sn 43), retrying > Jul 29 13:54:06 home wd0: soft error (corrected) > Jul 29 13:54:06 home wd0: soft error (corrected) > > > Thanks! > > RV
[no subject]
Folks, I had two crashes, on two different days, with the same reason: a dying hard drive. Definitively, it is really unpleasant to get caught with my pants down. There is a way to test hard drives for possible failures or foresee those errors? The SMART thing isn't that smart at all. Even after the server crashed twice due faulty harddrive, SMART keeps teeling me everything is OK. This is a SEAGATE SATA, only 1 year old. I'd expect a longer life of those drives. Am I wrong? Jul 30 13:23:36 home wd0 at pciide1 channel 0 drive 0: Jul 30 13:23:36 home wd0: 16-sector PIO, LBA48, 76319MB, 156301488 sectors Jul 30 13:23:36 home wd0(pciide1:0:0): using PIO mode 4, Ultra-DMA mode 5 Jul 29 13:53:55 home wd0(pciide1:0:0): timeout Jul 29 13:53:55 home type: ata Jul 29 13:53:55 home type: ata Jul 29 13:53:55 home c_bcount: 16384 Jul 29 13:53:55 home c_bcount: 16384 Jul 29 13:53:55 home c_skip: 0 Jul 29 13:53:55 home c_skip: 0 Jul 29 13:53:55 home pciide1:0:0: bus-master DMA error: missing interrupt, status=0x21 Jul 29 13:53:55 home pciide1:0:0: bus-master DMA error: missing interrupt, status=0x21 Jul 29 13:53:55 home wd0f: device timeout reading fsbn 1984192 of 1984192-1984223 (wd0 bn 30295888; cn 30055 tn 7 sn 7), retrying Jul 29 13:53:55 home wd0f: device timeout reading fsbn 1984192 of 1984192-1984223 (wd0 bn 30295888; cn 30055 tn 7 sn 7), retrying Jul 29 13:53:55 home wd0: soft error (corrected) Jul 29 13:53:55 home wd0: soft error (corrected) Jul 29 13:54:05 home wd0(pciide1:0:0): timeout Jul 29 13:54:05 home wd0(pciide1:0:0): timeout Jul 29 13:54:05 home type: ata Jul 29 13:54:05 home type: ata Jul 29 13:54:05 home c_bcount: 16384 Jul 29 13:54:05 home c_bcount: 16384 Jul 29 13:54:05 home c_skip: 0 Jul 29 13:54:05 home c_skip: 0 Jul 29 13:54:05 home pciide1:0:0: bus-master DMA error: missing interrupt, status=0x21 Jul 29 13:54:05 home pciide1:0:0: bus-master DMA error: missing interrupt, status=0x21 Jul 29 13:54:05 home wd0: transfer error, downgrading to Ultra-DMA mode 4 Jul 29 13:54:05 home wd0: transfer error, downgrading to Ultra-DMA mode 4 Jul 29 13:54:05 home wd0(pciide1:0:0): using PIO mode 4, Ultra-DMA mode 4 Jul 29 13:54:05 home wd0(pciide1:0:0): using PIO mode 4, Ultra-DMA mode 4 Jul 29 13:54:05 home wd0e: device timeout reading fsbn 1113568 of 1113568-1113599 (wd0 bn 12648112; cn 12547 tn 11 sn 43), retrying Jul 29 13:54:05 home wd0e: device timeout reading fsbn 1113568 of 1113568-1113599 (wd0 bn 12648112; cn 12547 tn 11 sn 43), retrying Jul 29 13:54:06 home wd0: soft error (corrected) Jul 29 13:54:06 home wd0: soft error (corrected) Thanks! RV
Re: OpenBSD's own compiler
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I was wondering, would it be a stupid and bad idea, for the OpenBSD team to develope, an OpenBSD C compiler based upon the OpenBSD security knowledge and internal standards regarding the language? yeah we will just drop everything we do now, quit all our jobs, send our families and other sos shopping at the mall in zimbabwe, not make a release for two years and produce the best compiler ever by then of course everybody will stop using openbsd for obvious reasons so we can finally all go drinking beer... Jeeez, talk about an overreaction to the suggestion. The GNU Compiler Collection has been something most people "put up with" as opposed to "enjoy" using. It's not that far fetched of an idea, remember a spin- off project that the OpenBSD guys are responsible that's become the most heavily used SSH code on the planet... Since nobody else has mentioned TeNDRA project, I might as well: http://www.tendra.org/ If you're interested in a BSD compiler collection, start by helping them out, it's been dormant (somewhat) but I'm certain it'd just take a few talented individuals with spare time to really get it going again. Cheers, - - -R. Tyler Ballance Lead Developer, bleep. LLC http://www.bleepsoft.com iD8DBQFEziNDqO6nEJfroRsRAisbAJ9QNotFvmY/WDqscfEqaXC5mkSsCwCfcATB G1z5mX5wkbEz5qPlnzpcQbw= =1Q3E -END PGP SIGNATURE-
Re: OpenBSD's own compiler
On Mon, Jul 31, 2006 at 02:12:47PM +0100, Steve Fairhead wrote: > Rico Secada [EMAIL PROTECTED] said: > > >> I read about how Ada is been used in all areas where safety is of great > issue, and about how it's being used in rockets, Boing Airplanes and so on > because of it's high level of safety. > > What I understood from it is, that the demand and control upon compilers, > rather than on the sourcecode, eliminates the possibility of a lot of errors > in the sourcecode, the compiler will not compile the program, and since Ada > is being used in a lot places, where lives dependt upon the software, it has > to be very safe. > > I was wondering, would it be a stupid and bad idea, for the OpenBSD team to > develope, an OpenBSD C compiler based upon the OpenBSD security knowledge > and internal standards regarding the language? yeah we will just drop everything we do now, quit all our jobs, send our families and other sos shopping at the mall in zimbabwe, not make a release for two years and produce the best compiler ever by then of course everybody will stop using openbsd for obvious reasons so we can finally all go drinking beer... cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: Silly^WFantastic OpenBSD promo video!!
On Mon, Jul 31, 2006 at 03:36:30PM +0200, Karel Kulhavy wrote: > ttyplay plays it like on 9600 baud terminal. When I increase the speed with > f it doesn't wait where it should. Not particularly useful. Either the > file is recorded incorrectly or the ttyplay works wrong. This has been fixed in ttyrec-1.0.8 (in CURRENT ports tree).
Re: Silly^WFantastic OpenBSD promo video!!
On Tue, Jul 25, 2006 at 02:32:32AM +0200, Moritz Grimm wrote: > Hello! > > > I made something ... and for some reason, several people liked it enough > to help it spread at reckless torrent speeds! > http://jolly.kicks-ass.org/OpenBSD_install-quick.avi.torrent should get Could you put it on archive.org so that people who have problems with torrent (I always had problems - the thing never seems to work reasonably) can download it too? CL< > you started, and with the friendly help of Nicholas Marriott -- who said > he'll keep the tracker running for about a week -- it should be there in > no time. > > Be warned, it's horribly geeky. There are people who will have no > understanding, whatsoever, for this. Yep, it was good revenge on the > flatmate for making me bring out the trash! (Most of it was his!!1) > Others may appreciate it a lot, so if you select your audience well, > this could be a special advocacy tool. ;) > > Please direct comments, flames and praise to me directly and don't > bother the list with them. Other than that, feel free to do whatever > your wish with that video, it's officially in the public domain, > trademarks belong to their respective owners, yadda yadda blah. > > > Moritz
Re: Looking to start developing OpenBSD
On Wed, Jul 26, 2006 at 12:19:45PM -0700, Nick Price wrote: > I'm interested in starting to do development on the OpenBSD OS. What are > some good tasks that need to be done that someone isn't currently working > on? Someone suggested ACPId, but apparently it's already being worked on. I suggest writing the driver for my I2C2P hardware, so people can tinker with I2C devices (like temperature sensors for RAID arrays, for which it was originally developed) connected over parallel port: http://i2c2p.twibright.com/ There's a driver for Linux kernel however I am not sure if it can be easily implemented in the OpenBSD kernel - allow an I2C bus be connected through parallel port :/ CL< > > Thanks > Nick
Re: Silly^WFantastic OpenBSD promo video!!
On Tue, Jul 25, 2006 at 09:19:33PM +0200, Matthias Kilian wrote: > On Tue, Jul 25, 2006 at 02:32:32AM +0200, Moritz Grimm wrote: > > Message-ID: <[EMAIL PROTECTED]> > > Date: Tue, 25 Jul 2006 02:32:32 +0200 > > From: Moritz Grimm <[EMAIL PROTECTED]> > > To: misc > > Subject: Silly^WFantastic OpenBSD promo video!! > > X-CRM114-Status: Good ( pR: 48.9362 ) > > http://jolly.kicks-ass.org/OpenBSD_install-quick.avi.torrent > > Slight waste of bandwidth but funny ;-) > > This is similar, but with qemu(1) over the emulated serial line, > recorded with ttyrec(1), i.e. much smaller: > > http://dead-parrot.de/01.install.tty (443K) > http://dead-parrot.de/02.setup.tty(262K) > http://dead-parrot.de/03.packages.tty (2.7M, rather boring) > > Replay with ttyplay(1), its in ports (misc/ttyrec). Or just run > telnet dead-parrot.de at the right time. ttyplay plays it like on 9600 baud terminal. When I increase the speed with f it doesn't wait where it should. Not particularly useful. Either the file is recorded incorrectly or the ttyplay works wrong. The manpage says -n Ignore the timing information in file which suggests that there should be some timing information in the file. CL< > > No sound, no colors, no comments. > > Ciao, > Kili
Re: OpenBSD's own compiler
Rico Secada [EMAIL PROTECTED] said: >> I read about how Ada is been used in all areas where safety is of great issue, and about how it's being used in rockets, Boing Airplanes and so on because of it's high level of safety. What I understood from it is, that the demand and control upon compilers, rather than on the sourcecode, eliminates the possibility of a lot of errors in the sourcecode, the compiler will not compile the program, and since Ada is being used in a lot places, where lives dependt upon the software, it has to be very safe. I was wondering, would it be a stupid and bad idea, for the OpenBSD team to develope, an OpenBSD C compiler based upon the OpenBSD security knowledge and internal standards regarding the language? Making it impossible for the compiler to accept and compile programs with all the knows errors which cause problems. The OpenBSDs way of programming has clearly made it clear, what security and quality is all about. << It's not just the compiler, it's the language. ADA is a heavily-constrained language. C is quite the opposite. ADA, IIRC, does not support interrupts (or other non-determistic events). The PC uses these quite a bit... Steve http://www.fivetrees.com
X-Orientation: Gay SMTP header
Hello who wouldn't mind other people knowing, please put X-Orientation: Gay into the SMTP headers. Thanks. Dumb people with anti-gay mindset usually use dumb mailers which don't show these lines. I have it so already for several years and no problem happened. I just figured out the author of a major software app is gay after I sent him a bugreport (and it was neither sendmail, nor BSD filesystem :) ). CL<
Re: VPN help needed: OpenBSD in the corporate environment instead of Linux
On Sat, Jul 29, 2006 at 12:22:42PM -0700, jeraklo wrote: > After summarizing all the clues I think I'll give a > chance to OpenVPN + OpenBSD 3.9 combination primarily > due to questionable quality of windows clients > IPsec+IP stack (as I said in my first post - windows > clients will comprise about 99% of all my VPN client > base). > > The differentiation between OS (OpenBSD) and the > service (OpenVPN package) will be clearly stated to > the upper management, including OpenBSD's proactive- > and overall security reputation. If you believe this'll work, be sure to make the difference clear. OpenVPN has some very nice security features, but seems to have more security bugs than would be considered reasonable in an OpenBSD application. Joachim
Re: BOB is dying.
How should I mark this message for Spamassassin? Spam or ham? Or delete it without giving to Spamassassin? :) CL< On Sun, Jul 16, 2006 at 02:54:35PM -0400, Tim Donahue wrote: > I swear, spam keeps getting wierder and wierder > > > On Fri, 14 Jul 2006 20:43:50 -0700 (PDT) > "Anon Y. Mous" <[EMAIL PROTECTED]> wrote: > > > BOB is dying. > > Right turn on RED. > > Tired of spam? Yahoo! Mail has the best spam protection around > > http://mail.yahoo.com
More to hanging audio
I examined dmesg, there were no late messages. Tried shutting down X Windows
and playing from console. Didn't help. Reboot helped. My dmesg:
OpenBSD 3.9 (GENERIC) #617: Thu Mar 2 02:26:48 MST 2006
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel(R) Pentium(R) M processor 1.50GHz ("GenuineIntel" 686-class) 1.50
GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,ACPI,MMX,FXSR,SSE,SSE2,SS,TM,SBF,EST,TM2
cpu0: Enhanced SpeedStep 1500 MHz (1340 mV) (not in table)
real mem = 535052288 (522512K)
avail mem = 481202176 (469924K)
using 4278 buffers containing 26857472 bytes (26228K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(00) BIOS, date 01/28/05, BIOS32 rev. 0 @ 0xffe90
pcibios0 at bios0: rev 2.1 @ 0xf/0x1
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfc590/176 (9 entries)
pcibios0: PCI Interrupt Router at 000:31:0 ("Intel 82371 ISA and IDE" rev 0x00)
pcibios0: PCI bus #2 is the last bus
bios0: ROM list: 0xc/0xd800! 0xcd800/0x800 0xce000/0x800 0xce800/0x800
0xcf000/0x800 0xcf800/0x800
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "Intel 82852GM Hub-PCI" rev 0x02
"Intel 82852GM Memory" rev 0x02 at pci0 dev 0 function 1 not configured
"Intel 82852GM Configuration" rev 0x02 at pci0 dev 0 function 3 not configured
vga1 at pci0 dev 2 function 0 "Intel 82852GM AGP" rev 0x02: aperture at
0xf000, size 0x800
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
"Intel 82852GM AGP" rev 0x02 at pci0 dev 2 function 1 not configured
uhci0 at pci0 dev 29 function 0 "Intel 82801DB USB" rev 0x01: irq 11
usb0 at uhci0: USB revision 1.0
uhub0 at usb0
uhub0: Intel UHCI root hub, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1 at pci0 dev 29 function 1 "Intel 82801DB USB" rev 0x01: irq 11
usb1 at uhci1: USB revision 1.0
uhub1 at usb1
uhub1: Intel UHCI root hub, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
uhci2 at pci0 dev 29 function 2 "Intel 82801DB USB" rev 0x01: irq 11
usb2 at uhci2: USB revision 1.0
uhub2 at usb2
uhub2: Intel UHCI root hub, rev 1.00/1.00, addr 1
uhub2: 2 ports with 2 removable, self powered
ehci0 at pci0 dev 29 function 7 "Intel 82801DB USB" rev 0x01: irq 11
usb3 at ehci0: USB revision 2.0
uhub3 at usb3
uhub3: Intel EHCI root hub, rev 2.00/1.00, addr 1
uhub3: 6 ports with 6 removable, self powered
ppb0 at pci0 dev 30 function 0 "Intel 82801BAM Hub-to-PCI" rev 0x81
pci1 at ppb0 bus 1
cbb0 at pci1 dev 1 function 0 "Texas Instruments PCI4510 CardBus" rev 0x02: irq
11
"Texas Instruments PCI4510 FireWire" rev 0x00 at pci1 dev 1 function 1 not
configured
ipw0 at pci1 dev 3 function 0 "Intel PRO/Wireless 2100" rev 0x04: irq 11,
address 00:0c:f1:61:60:36
fxp0 at pci1 dev 8 function 0 "Intel PRO/100 VE" rev 0x81, i82562: irq 11,
address 00:11:43:52:46:e7
inphy0 at fxp0 phy 1: i82562ET 10/100 PHY, rev. 0
cardslot0 at cbb0 slot 0 flags 0
cardbus0 at cardslot0: bus 2 device 0 cacheline 0x8, lattimer 0x20
pcmcia0 at cardslot0
ichpcib0 at pci0 dev 31 function 0 "Intel 82801DBM LPC" rev 0x01: SpeedStep
pciide0 at pci0 dev 31 function 1 "Intel 82801DBM IDE" rev 0x01: DMA, channel 0
configured to compatibility, channel 1 configured to compatibility
wd0 at pciide0 channel 0 drive 0:
wd0: 16-sector PIO, LBA48, 38154MB, 78140160 sectors
wd0(pciide0:0:0): 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: SCSI0 5/cdrom
removable
cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2
auich0 at pci0 dev 31 function 5 "Intel 82801DB AC97" rev 0x01: irq 11, ICH4
AC97
ac97: codec id 0x83847650 (SigmaTel STAC9750/51)
ac97: codec features headphone, 20 bit DAC, 20 bit ADC, SigmaTel 3D
audio0 at auich0
isa0 at ichpcib0
isadma0 at isa0
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
pms0 at pckbc0 (aux slot)
pckbc0: using irq 12 for aux slot
wsmouse0 at pms0 mux 0
pcppi0 at isa0 port 0x61
midi0 at pcppi0:
spkr0 at pcppi0
npx0 at isa0 port 0xf0/16: using exception 16
pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
biomask efed netmask efed ttymask ffef
pctr: 686-class user-level performance counters enabled
mtrr: Pentium Pro MTRR support
uhidev0 at uhub1 port 1 configuration 1 interface 0
uhidev0: Logitech USB-PS/2 Optical Mouse, rev 2.00/20.00, addr 2, iclass 3/1
ums0 at uhidev0: 3 buttons and Z dir.
wsmouse1 at ums0 mux 0
dkcsum: wd0 matches BIOS drive 0x80
root on wd0a
rootdev=0x0 rrootdev=0x300 rawdev=0x302
auich0: measured ac97 link rate at 48003 Hz, will use 48000 Hz
Audio hangs in 3.9
My xmms crashed so I killed it and make sure no more xmms process is running there. Then I tried XMMS several times again and every time I pressed play it hangs. I read all the process names and there is no remain if xmms. mplayer does the same - hangs on opening audio. Is the audio in OpenBSD kernel hanging or what? CL<
Re: rule help
On Sun, Jul 30, 2006 at 10:33:56PM -0700, S t i n g r a y wrote:
> can you please help me out here ..
>
> below is my pf.conf file which allow all ourbound
> traffice , now i want it to only allow specific
> protocols like only http,https,ftp,.
>
> need a hint.
<...>
> pass out on $extif inet proto { icmp, udp, tcp } keep state
tcp/udp rules can also take a list of ports.
W = "80 443"
pass proto { tcp udp } from any to any port { $W }
--
jared
[ openbsd 3.9-current GENERIC ( jul 29 ) // i386 ]
Re: 3.9 freeze
Pedro, since I set the "option NKMEMPAGES_MAX=65535" on kernel file, the server doesn't freeze UVM amap128305 10153K 50705K157284K4071891000 0 16,32,64,128,256,512,1024,2048,4096,8192,16384,32768,65536 This server has an uptime 12 days, before the change only alive 3 or 4 days regards,. - Original Message - From: "Pedro Martelletto" <[EMAIL PROTECTED]> To: "Federico Giannici" <[EMAIL PROTECTED]> Cc: ; "diego" <[EMAIL PROTECTED]> Sent: Saturday, July 29, 2006 2:00 PM Subject: Re: 3.9 freeze Any news on this? -p.
unrecognized Waveplus 802.11b chip
> I bought a cheapy PCI Wifi card awhile back. Looking at the card I see > a what I assume it the wifi chip which reads: > WAVE > WP1200 DLQF > MK47061.1 0404 > > I thought this was a wi(4) when I bought it but now I see that it is > now. Sure enough, OpenBSD 3.9 doesn't recognize it: > # dmesg | grep net > unknown vendor 0x17f7 product 0x0001 (class network subclass > miscellaneous, rec 0x01) at pci0 dev 15 function 0 not configured > > Here is the page for the chip: http://www.waveplus.com/wp1200.asp > And here is what seems to be the entire technical specs: > http://www.waveplus.com/download/wp1200_datasheet.pdf > > Is any developer interested in supporting this? I'd be willing to > donate my card. looks like another opendoc-friendly Taiwanese wireless chips vendor. cool!
Re: bufcachepercent & samba
Craig Hammond wrote: I am setting up a Samba fileserver on obsd 3.9-stable I noticed that up until obsd3.3, in section 11 of the faq, it recommended increasing bufcachepercent for fileservers with lots of free memory. Now there is no section 11 at all in the faq. For a box that is basically only going to do Samba, is it still ok to increase bufcachepercent to speed things up, and if so, are there any limits I should be aware of? Obviously I wouldn't set it to 95% but with 1 gb of RAM, is 50% ok. did you read the commit message? http://www.openbsd.org/cgi-bin/cvsweb/www/faq/faq11.html See revision 1.50... "Remove some bad stuff... NMBCLUSTERS gets people into serious trouble, as does BUFCACHEPERCENT. Removed." The problem with documenting knobs like that is people feel the need to twist 'em. In the process, they demonstrate why OpenBSD developers set things the way they are...though they rarely see the performance and stability problems they caused as a direct result of their actions. Rather, they whine that "OpenBSD doesn't work!" and waste a lot of people's time until we eventually find out that little detail they creatively left out. THINK A MOMENT... If there was one magical setting which was Always Best, don't you think that maybe the OpenBSD developers would have set it there? IF you want to twist knobs, start from the default, see if you can find a real problem (note: if performance isn't absolutely as fast as need be, that's not a problem if you are pulling one 100k file off the server once a minute. It may be a problem if you are pulling those same files many times a second). IF you spot a real problem, then twist just the appropriate knobs, and see what happens. "Bigger" is not always better, it isn't always even faster. Nick.
Re: Gimp segfaults
On 7/31/06, Karel Kulhavy <[EMAIL PROTECTED]> wrote: >I noticed there are two Gimps in the ports, I tried both (2.2.10 and >2.2.10p0) ports-related messages reach a more appropriate audience on ports@ >and both segfault in the same place. It displays a speedometer with Wilber, >does several thermometers loading whatever, and then it segfaults. Does it >happen only for me or for everyone? Machine arch? OS version? Are you compiling the port yourself or using a package? (try the other to help rule out build problems).
Re: Gimp segfaults
On 7/31/06, Karel Kulhavy <[EMAIL PROTECTED]> wrote: I noticed there are two Gimps in the ports, I tried both (2.2.10 and 2.2.10p0) and both segfault in the same place. It displays a speedometer with Wilber, does several thermometers loading whatever, and then it segfaults. Does it happen only for me or for everyone? Gimp works for me under VMWare and on a Compaq Presario. You went through the installer right? After doing pkg_add gimp, running 'gimp' should bring up an installer where you set things like your data directories. I mention this because in your trace there's things like "gimpdatafiles.c". Perhaps you missed the installer or you set things wrongly in it? -Nick
Re: stopping robots
I've got a robots.txt, and a script that loops to infinity. Actually, it's a useful page on the server, there's a list that can be ordered two ways, and switching from one to the other increments a parameter at the end of the invocation. A robot has no business reading that specific page in the first place (in fact, they're disallowed to), and after a small number of loops (10 or 15), the webserver becomes very unresponsive, thus ensuring the robot writer will lose a lot of time on that page. Assuming reasonable technologies (e.g., mason), the url does not even have to look like a script...
Gimp segfaults
I noticed there are two Gimps in the ports, I tried both (2.2.10 and 2.2.10p0)
and both segfault in the same place. It displays a speedometer with Wilber,
does several thermometers loading whatever, and then it segfaults. Does it
happen only for me or for everyone?
CL<
#0 0x016a4e90 in ?? ()
No symbol table info available.
#1 0x08730a57 in _dl_thread_kern_go () from /usr/libexec/ld.so
No symbol table info available.
#2 0x08730794 in dlclose () from /usr/libexec/ld.so
No symbol table info available.
#3 0x036c8edb in _g_module_close ()
from /usr/local/lib/libgmodule-2.0.so.800.4
No symbol table info available.
#4 0x036c9991 in g_module_close () from /usr/local/lib/libgmodule-2.0.so.800.4
No symbol table info available.
#5 0x027e6f37 in gimp_module_close (module=0x7db01500) at gimpmodule.c:491
No locals.
#6 0x027e6a6e in gimp_module_new (filename=0x88c18ac0 "", load_inhibit=0,
verbose=0) at gimpmodule.c:274
module = (GimpModule *) 0x7db01500
#7 0x027e7701 in gimp_module_db_module_initialize (file_data=0xcfbd4b40,
user_data=0x89954740) at gimpmoduledb.c:391
db = (GimpModuleDB *) 0x89954740
module = (GimpModule *) 0xcfbd4b40
load_inhibit = 23744144
#8 0x02681d23 in gimp_datafiles_read_directories (
path_str=0x16a4e90 ,
---Type to continue, or q to quit---
flags=G_FILE_TEST_EXISTS,
loader_func=0x27e7690 ,
user_data=0x89954740) at gimpdatafiles.c:182
file_data = {
filename = 0x7fa6e540 "/usr/local/lib/gimp/2.0/modules/libcdisplay_proof.so",
dirname = 0x83e10e00 "/usr/local/lib/gimp/2.0/modules",
basename = 0x7cdcb088 "libcdisplay_proof.so", atime = 1154339688,
mtime = 1152455764, ctime = 1154206067}
filestat = {st_dev = 0, st_ino = 2582392, st_mode = 33261,
st_nlink = 1, st_uid = 0, st_gid = 7, st_rdev = 15576384,
st_lspare0 = -802068552, st_atimespec = {tv_sec = 1154339688,
tv_nsec = 6952}, st_mtimespec = {tv_sec = 1152455764, tv_nsec = 0},
st_ctimespec = {tv_sec = 1154206067, tv_nsec = 8}, st_size = 18666,
st_blocks = 40, st_blksize = 16384, st_flags = 0, st_gen = 0,
st_lspare1 = 0, __st_birthtimespec = {tv_sec = 0, tv_nsec = -696016892},
st_qspare = {2804194459078974040, -293425854058496}}
local_path = (
gchar *) 0x7fa6e400
"/home/clock/.gimp-2.2/modules:/usr/local/lib/gimp/2.0/modules"
path = (GList *) 0x7d08a09c
list = (GList *) 0x7d08a0a8
filename = (
gchar *) 0x7fa6e540 "/usr/local/lib/gimp/2.0/modules/libcdisplay_proof.so"
---Type to continue, or q to quit---
err = 23744144
dir = (GDir *) 0x7ca32810
dir_ent = (const gchar *) 0x7cdcb088 "libcdisplay_proof.so"
#9 0x027e7520 in gimp_module_db_load (db=0x89954740,
module_path=0x7fa6e440
"/home/clock/.gimp-2.2/modules:/usr/local/lib/gimp/2.0/modules") at
gimpmoduledb.c:298
No locals.
#10 0x1c11e1f6 in ?? ()
No symbol table info available.
#11 0x89954740 in ?? ()
No symbol table info available.
#12 0x7fa6e440 in ?? ()
No symbol table info available.
#13 0x in ?? ()
No symbol table info available.
unrecognized Waveplus 802.11b chip
I bought a cheapy PCI Wifi card awhile back. Looking at the card I see a what I assume it the wifi chip which reads: WAVE WP1200 DLQF MK47061.1 0404 I thought this was a wi(4) when I bought it but now I see that it is now. Sure enough, OpenBSD 3.9 doesn't recognize it: # dmesg | grep net unknown vendor 0x17f7 product 0x0001 (class network subclass miscellaneous, rec 0x01) at pci0 dev 15 function 0 not configured Here is the page for the chip: http://www.waveplus.com/wp1200.asp And here is what seems to be the entire technical specs: http://www.waveplus.com/download/wp1200_datasheet.pdf Is any developer interested in supporting this? I'd be willing to donate my card. Thank you in advance, -Nick
