Re: named rc.d
On 02/08/06, Mark Andrews <[EMAIL PROTECTED]> wrote: > Apologies if posted to wrong list, the rc.d script for named chowns > /etc/namedb to root:wheel if set to bind:bind why is this? A slave > named server running as bind user cannot download new slave zones if > dir ownership is root or update it if file ownerships are root which I > sometimes see. Use /etc/namedb/slave for slave zone. Use /etc/namedb/dynamic for dynamic zone. Mark # $FreeBSD: src/etc/mtree/BIND.chroot.dist,v 1.6 2004/11/04 05:24:29 gshapiro Exp $ # # Please see the file src/etc/mtree/README before making changes to this file. # /set type=dir uname=root gname=wheel mode=0755 . dev mode=0555 .. etc namedb dynamic uname=bind .. master .. slave uname=bind .. .. .. /set type=dir uname=bind gname=wheel mode=0755 var uname=root dump .. log .. run named .. .. stats .. .. .. > Chris > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: [EMAIL PROTECTED] thanks to all, I see now. So using the subdir is the correct way. Chris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Re: bce0: Error mapping mbuf into TX chain!
On Fri, Aug 04, 2006 at 03:52:40PM +0200, Scott Wilson wrote: > On 7/13/06, Doug Ambrisko <[EMAIL PROTECTED]> wrote: > >David (Controller AE) Christensen writes: > >| Sorry, I've been out on vacation and just got back into town. I'll MFC > >| the patch within the next day or two. > > > >I'll let you merge in the down/up fix that I put into -current. > > > >Doug A. > > Hi, I just had a bce interface lock up with the same problem: > > Aug 4 07:00:16 pe3 kernel: bce0: /usr/src/sys/dev/bce/if_bce.c(4644): > Error mapping mbuf into TX chain! > Aug 4 07:00:47 pe3 last message repeated 368 times > > > running v 1.2.2.5 of if_bce.c from RELENG_6 which has the > defragmentation patch mentioned in this thread. Any suggestions on > how I can help find a fix? > > scott Hmm... I can see several bus_dma(9) related bugs in bce(4). For architectures that have IOMMU hardware it may have corrupted DMA mapping and I'm pretty sure it wouldn't work on sparc64. When it has to handle many fragmented frame or has insufficient number of free Tx descriptors it would show unexpected results. Unfortunately I don't have hardwares supported by bce(4) and fixing requiries a working hardware. :-( -- Regards, Pyun YongHyeon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: iir(4) driver (Was: Re: Safe card to replace for ICP Vortex GDT851...)
Scott Long wrote this message on Tue, Aug 01, 2006 at 09:35 -0600: > FreeBSD. Making big statements in public that they don't, or that it's > not up to ones' standards or hopes, isn't terribly useful or productive. > I'd hate for FreeBSD to turn into That Other BSD that publically abuses > and harasses vendors for percieved sleights. There are much more > positive and product ways to fix problems and form good relationships, > and those ways are actively being pursued by some people right now. The problem is that these pursuits are not public knowlege, and very often trying to get support through even better than normal channels (i.e. using your system builder's extra clout) doesn't get you this info... The most they tell you is sorry, no support, and we are just being nice to even tell you this since you're running something else... I believe that honest information is better than hopes that turn up fruitless... I've had no end of issues w/ Intel trying to get them to fix various issues w/ their cards (SRCU31A and SRCU42L), and they won't even acknowledge that failing drives due to SELECTION_TIMEOUT, ABORTED COMMAND, OVERLAPPED COMMANDS ATTEMPTED or DISCONNECT_TIMEOUT is a major issue... Due to the fact that SRCU31A is so old, they haven't qualified the newer 2.42 firmware w/ the card... We are going to look at it, since we haven't seen any "failed" hd's on the 2.42 firmware... > And here again is my standard disclaimer: > I highly recommend that anyone who takes their data integrity seriously > should spend time qualifying any RAID solution that they are interested > in before putting it into production. What works for your workload > might not work for someone else's workload, and vice-versa. Agreed, luckily we found the hang issue w/ 5.x before we shipped, so we were saved yet another disaster... > Patrick M. Hausen wrote: > >Hello! > > > > > >>'k, just to clarify here ... the new products won't be based on the > >>iir(4) driver then? > > > > > >Yes, they won't. > > > > > >>Basically, should the iir(4) driver be considered EOE also? > > > > > >As far as Adaptec and ICP Vortex are concerned, yes. Since the > >driver is Open Source, there is no enforced EOE, just "orphanage", > >if nobody is willing to work on it. > To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [IMPORTANT] Adaptec no longer supporting iir(4) driver ...
On Fri, 4 Aug 2006, John-Mark Gurney wrote: User Freebsd wrote this message on Mon, Jul 31, 2006 at 22:44 -0300: For those that haven't been following the discussion on this, the iir(4) driver in FreeBSD 6.x appears to have a deadlock issue under medium to heavy load, where the 'blocked' state just continues to rise until file accesses just no longer work ... So, if you are running a server that is using the iir(4) device driver and are considering upgrading to FreeBSD 6.x and beyond, or are looking to build a new machine using a device that relies on this driver, do so at your own peril ... Please note that this deadlock issue exists on *both* the ICP Vortex cards, *and* the Intel based RAID controllers ... Have you tried the driver in -current and/or 6.1-R? Specificly v1.14 and v1.13.2.1 of iir.c that limits the simq to 32 commands? We are running w/ this modifications w/o issues on 6.0-R w/ SRCU31A and SRCU42L cards... We have a few GDT cards also that I don't believe we are having any issues with... Yes, this was the first thing ScottL asked when we narrowed the problem down ... this appears to be a different issue then the one you were seeing :( Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [IMPORTANT] Adaptec no longer supporting iir(4) driver ...
User Freebsd wrote this message on Mon, Jul 31, 2006 at 22:44 -0300: > For those that haven't been following the discussion on this, the iir(4) > driver in FreeBSD 6.x appears to have a deadlock issue under medium to > heavy load, where the 'blocked' state just continues to rise until file > accesses just no longer work ... > > So, if you are running a server that is using the iir(4) device driver and > are considering upgrading to FreeBSD 6.x and beyond, or are looking to > build a new machine using a device that relies on this driver, do so at > your own peril ... > > Please note that this deadlock issue exists on *both* the ICP Vortex > cards, *and* the Intel based RAID controllers ... Have you tried the driver in -current and/or 6.1-R? Specificly v1.14 and v1.13.2.1 of iir.c that limits the simq to 32 commands? We are running w/ this modifications w/o issues on 6.0-R w/ SRCU31A and SRCU42L cards... We have a few GDT cards also that I don't believe we are having any issues with... Infact, scottl tracked down that change after a bit of proding from me on behalf of my employer nCircle... (Though it helped that he was able to reproduce it in his lab.)... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
No ACPI thermal zones on AMI BIOS?
I know this has been discussed prior to my recent posting. On two boxes running FreeBSD 6.1-STABLE with AMI BIOS neither thermal-zones nor fan speed information is provided as OID (looking at this via sysctl hw.acpi). One box is a ASUS A8N32-SLI Deluxe, most recent (AMI-) BIOS 1205, running FreeBSD 6.1-STABLE/AMD64 (no 32Bit compatibility) as built with the most recent FreeBSD 6.1-code available via CVS. The other box is at my lab a ASUS P4P800 i386 box, quite old compared to the AMD64 box, but also equipted with an AMI BIOS. This box also does not show any thermal zones and/or fand speed information via ACPI as it should expected due to its age. I had another AMD64 box, based on ASUS A8N-SLI Deluxe, with AWARD BIOS and there I saw theraml zones and fan speed informations via sysctl, mbmon/xmbmon was useable on that board, while this tool isn't on the above first mentioned. What is the difference between these BIOSes in handling these health-important informations and why are these infos aren't accessible in FreeBSD? Regards, Oliver ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Re: bce0: Error mapping mbuf into TX chain!
On 7/13/06, Doug Ambrisko <[EMAIL PROTECTED]> wrote: David (Controller AE) Christensen writes: | Sorry, I've been out on vacation and just got back into town. I'll MFC | the patch within the next day or two. I'll let you merge in the down/up fix that I put into -current. Doug A. Hi, I just had a bce interface lock up with the same problem: Aug 4 07:00:16 pe3 kernel: bce0: /usr/src/sys/dev/bce/if_bce.c(4644): Error mapping mbuf into TX chain! Aug 4 07:00:47 pe3 last message repeated 368 times running v 1.2.2.5 of if_bce.c from RELENG_6 which has the defragmentation patch mentioned in this thread. Any suggestions on how I can help find a fix? scott ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: freebsd 6.x and 3ware 9500S-8 in 32bit pci slot
Hi, How often is this crash? (daily, weekly, monthy...) What's the freebsd version you're using? Can you try your card in an other PCI slot and do you have other PCI devices? Does this reset and/or crash could be related to high i/o or something else? We have a similar, but a 4port (9500S-4) controller with 5.5 and in a PCI-X and works fine. 64bit support in freebsd differs from the PCI 64bit. In a PCI-X slot, the 64bit is the databus "width", instead of the normal 32bit. You can's enforce it, but it works automatically in PCI-X slots. (A dmesg and a crash dump, if you can provide it, would be nice for the developer guys imho.) Regards, Andrej Ville Sulin wrote: Hi, I have a smallish problem, got a backup server with ASUS PC-DL motherboard that doesn't have a 64 bit pci slot and a 3ware 9500S-8 card. The machine resets the controller every now and then, but when there's enough disk io when it tries to do that the machine crashes. console warnings: twa0: INFO: (0x04: 0x000c): : unit=0 twa0: ERROR: (0x05: 0x210b): Request timed out!: request = 0xc64fb1f0 twa0: INFO: (0x16: 0x1108): Resetting controller...: twa0: INFO: (0x04: 0x0001): : SoftResetCount=1 twa0: INFO: (0x16: 0x1107): Controller reset done!: twa0: INFO: (0x04: 0x000c): : unit=0 lspci -vv : 03:0b.0 RAID bus controller: 3ware Inc 9xxx-series SATA-RAID Subsystem: 3ware Inc 9xxx-series SATA-RAID Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
freebsd 6.x and 3ware 9500S-8 in 32bit pci slot
Hi, I have a smallish problem, got a backup server with ASUS PC-DL motherboard that doesn't have a 64 bit pci slot and a 3ware 9500S-8 card. The machine resets the controller every now and then, but when there's enough disk io when it tries to do that the machine crashes. console warnings: twa0: INFO: (0x04: 0x000c): : unit=0 twa0: ERROR: (0x05: 0x210b): Request timed out!: request = 0xc64fb1f0 twa0: INFO: (0x16: 0x1108): Resetting controller...: twa0: INFO: (0x04: 0x0001): : SoftResetCount=1 twa0: INFO: (0x16: 0x1107): Controller reset done!: twa0: INFO: (0x04: 0x000c): : unit=0 lspci -vv : 03:0b.0 RAID bus controller: 3ware Inc 9xxx-series SATA-RAID Subsystem: 3ware Inc 9xxx-series SATA-RAID Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Web Camera for stable
Anton Nikiforov wrote: Dear All, Does someone have some web cam working with Free BSD-stable? What cameras you are using and what software? (picture download or video stream - it doesnot matter) I was trying to google the net and find solutions with gphoto and vid. All this solutions are based on old cameras that i cannot find on the market. (Gphoto supports a lot of cameras, but most of them are not web cams) Maybe you can try the freebsd port of the pwc linux driver. It is reported to work with various webcams. The pwcbsd project URL is : http://raaf.atspace.org I hope it helps. Greetings, Emil ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em(4) update for 6-STABLE
On Thu, Aug 03, 2006 at 04:14:35PM -0700, Nikolas Britton wrote: N> >First, it significantly improves perfromance of the driver N> >under high pps load. N> >Second, it adds support for few new chips. N> > N> >You need to update your system to fresh RELENG_6. The driver N> >will not compile on 6.1-RELEASE. N> N> Why will it not compile on 6.1? Because it uses new taskqueue API not yet present in 6.1-RELEASE. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Web Camera for stable
Anton Nikiforov <[EMAIL PROTECTED]> wrote: > Does someone have some web cam working with Free BSD-stable? > What cameras you are using and what software? (picture download or video > stream - it doesnot matter) Sure. I have a standard cheap PAL camera with composite output (cinch connector). It's connected to a PCI video capture card witg bt848 / bt878 chip (only few bucks on eBay), using the bktr(4) driver. Works perfectly fine with all versions of FreeBSD, from 4.x to current. > I was trying to google the net and find solutions with gphoto and vid. > All this solutions are based on old cameras that i cannot find on the > market. Simple PAL (or NTSC) cameras can be found for small prices everywhere (well, at least over here in Germany). They're commonly used for surveillance purposes etc. There are several German shops who sell them for about 50 Euros. Another possibility is to use an IP camera, which are about 100 Euros. They are completely OS-independent and connect directly to an ethernet network (some also have wireless WLAN); they support standard protocols such as HTTP, FTP and telnet. USB cameras are very, very cheap, but they're really not worth much. The quality is often bad, and you never can tell for sure whether you can make them work with FreeBSD, except by actually trying it. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. cat man du : where Unix geeks go when they die ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
