Re: REPOST for archive: Re: nscd again (nis client cache) patch for 6 stable branch
Hi guys, I've just got my patch for nscd backport for 6.4-p4 tested and woring fine. You can find it here: http://valqk.com/nscd_fbsd_6/ I hope it's useful for someone. cheers, valqk. Anton - Valqk написа: > I've been searching in the mailist archives and never found this, so > I'm reposting for archiving purposes. > > According to Denis Barov : > > Gzipped patch avialable at > http://www.dindin.ru/wiki/FreeBSD?action=AttachFile&do=get&target=nscd_backport.gz > > (78Kb) > > Mon, Dec 24, 2007 at 12:15 +0300 Denis Barov: >> > Hi, Michael! >> > In attachment patch for backporing nscd from RELENG_7 to RELENG_6. >> Tested on >> > > FreeBSD sepulca.yandex.ru 6.3-PRERELEASE FreeBSD 6.3-PRERELEASE >> #0: Thu Dec >> > 23 22:06:36 MSK 2007 >> > r...@sepulca.yandex.ru:/usr/obj/usr/RELENG_6_ncsd/src/sys/GENERIC >> amd64 >> > > and works fine. >> > > Must I prepare pr? >> > > P.S. Don't forget to mkdir -p src/usr.sbin/nscd/agents before >> patching ;) > > > > > On Wed, Jan 23, 2008 at 11:52:21AM +0200, Anton - Valqk wrote: > > Is there nscd/cached for STABLE 6 branch or it's only implemented in > 7.X? > > Adam McDougall wrote: > > I wanted to say Thanks!!! for this example, because before this point > > I was under the impression that nscd/cached was of no use for NIS > clients, > > only LDAP or maybe other directory systems that I don't use. I tried > > "cache compat" as below for passwd and group and it works! Our NIS > > entries at work are big enough that without the cache, top takes > 7+ seconds to > > open, ssh login takes a few seconds, and samba logins were > concerningly > > slow. I did not try samba connections, but the other methods are > much > > faster now on the second run. Wanted to post this for the archive > too. > > > > On Sat, Jan 19, 2008 at 02:17:11PM +0300, Michael Bushkov wrote: > > > > Hi Denis, > > Several things: > > 1. You definitely can't use cache for *_compat sources. I mean > lines like > > "group_compat: cache nis" aren't supported. > > 2. Cache should work ok with the configuration you've mentioned > in your > > first example, i.e.: "group: cache compat". Just checking - why > do you > > think that cache isn't working? The correct way to determine it > is to > > perform the same query twice. During the first pass (when query > is not > > cached), the request will be processed by NIS module and you'll > have all > > the NIS-related stuff in the logs. On the second pass the > request should be > > handled by scd module - and you shouldn't see any activity in > NIS logs. It > > would be great to see the debug log (with nscd log turned on) > separately - > > for the first and the second pass. It would help to find the > error in nscd, > > if there is one. > > > > With best regards, > > Michael Bushkov > > > > On Jan 17, 2008, at 9:55 PM, Denis Barov wrote: > > > > > >>> Hello! > >>> > >>> I found some strange behaviour of NIS/nscd when NIS in compat > mode. In > >>> /etc/nsswitch.conf I have: > >>> > >>> netgroup: cache compat > >>> passwd: cache compat > >>> group:cache compat > >>> > > ___ > > freebsd-stable@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to > "freebsd-stable-unsubscr...@freebsd.org" > > > > > > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: php-cgi frozen with sbwait when SMP enable
You can try taking look to lighttpd status and fcgi processes status like this: server.modules += ( "mod_status" ) status.status-url = "/server-status" status.statistics-url = "/sstatus1" status.statistics-url gives info for each fastcgi like this: fastcgi.active-requests: 0 fastcgi.backend.backend1.0.connected: 12493970 fastcgi.backend.backend1.0.died: 0 fastcgi.backend.backend1.0.disabled: 0 fastcgi.backend.backend1.0.load: 0 fastcgi.backend.backend1.0.overloaded: 0 fastcgi.backend.backend1.load: 1 fastcgi.requests: 19479062 etc... read what each means on lighttpd site... pls tell what caused this, it'd be very interesting to me! cheers, valqk. Ken Chen wrote: > I capture something. > > Please check the PID 57776. It's CPU time never change since my previous > mail here. > > web4# ps alx | grep php-cgi | grep -v grep | grep sbwait > 65534 57776 47240 0 4 0 182328 84984 sbwait I ??2:02.12 > /usr/local/bin/php-cgi > 65534 57801 47240 0 4 0 182328 82408 sbwait I ??0:19.97 > /usr/local/bin/php-cgi > 65534 57809 47240 0 4 0 182328 84096 sbwait I ??1:12.03 > /usr/local/bin/php-cgi > 65534 57823 47240 0 4 0 182328 84492 sbwait I ??2:04.21 > /usr/local/bin/php-cgi > 65534 57833 47240 0 4 0 183352 83316 sbwait I ??0:28.62 > /usr/local/bin/php-cgi > 65534 57866 47240 0 4 0 182328 79952 sbwait I ??0:05.92 > /usr/local/bin/php-cgi > 65534 57870 47240 0 4 0 182328 83184 sbwait I ??0:56.83 > /usr/local/bin/php-cgi > 65534 57871 47240 0 4 0 182328 83388 sbwait I ??0:54.96 > /usr/local/bin/php-cgi > 65534 57891 47240 0 4 0 182328 84436 sbwait I ??1:58.32 > /usr/local/bin/php-cgi > 65534 57925 47240 0 4 0 182328 84380 sbwait I ??2:03.53 > /usr/local/bin/php-cgi > 65534 65944 47240 0 4 0 182328 84184 sbwait I ??0:39.97 > /usr/local/bin/php-cgi > 65534 65952 47240 0 4 0 182328 84408 sbwait I ??0:21.37 > /usr/local/bin/php-cgi > 65534 66007 47240 0 4 0 183352 90960 sbwait I ??1:16.81 > /usr/local/bin/php-cgi > 65534 66014 47240 5 4 0 182328 92748 sbwait S ??1:41.23 > /usr/local/bin/php-cgi > 65534 66038 47240 1 4 0 182328 91900 sbwait I ??1:38.04 > /usr/local/bin/php-cgi > 65534 66060 47240 0 4 0 182328 90048 sbwait I ??1:15.46 > /usr/local/bin/php-cgi > 65534 66078 47240 3 4 0 182328 92224 sbwait S ??1:39.66 > /usr/local/bin/php-cgi > web4# top -b > last pid: 70768; load averages: 1.62, 1.65, 1.43 up 4+15:56:06 > 22:53:48 > 85 processes: 1 running, 84 sleeping > > Mem: 492M Active, 1204M Inact, 218M Wired, 60M Cache, 112M Buf, 27M Free > Swap: 2019M Total, 20K Used, 2019M Free > > > PID USERNAME THR PRI NICE SIZERES STATE C TIME WCPU COMMAND > 69544 nobody 1 80 203M 38500K nanslp 1 6:31 11.33% php > 47290 nobody 1 40 101M98M kqread 1 30:42 2.98% lighttpd > 66526 nobody 1 40 178M 92796K accept 1 1:40 1.12% php-cgi > 66077 nobody 1 40 178M 92512K accept 0 1:49 1.07% php-cgi > 65921 nobody 1 40 178M 92696K accept 0 1:43 0.98% php-cgi > 65968 nobody 1 40 178M 92484K accept 0 1:43 0.93% php-cgi > 66017 nobody 1 40 178M 92444K accept 0 1:50 0.88% php-cgi > 65979 nobody 1 40 178M 92676K accept 1 1:44 0.88% php-cgi > 66424 nobody 1 40 178M 92928K accept 1 1:36 0.88% php-cgi > 65938 nobody 1 40 178M 92336K accept 1 1:52 0.73% php-cgi > 65951 nobody 1 40 178M 92704K accept 0 1:48 0.73% php-cgi > 66016 nobody 1 40 178M 92232K accept 1 1:41 0.73% php-cgi > 65950 nobody 1 40 178M 93192K accept 0 1:51 0.68% php-cgi > 65999 nobody 1 40 178M 92940K accept 1 1:46 0.63% php-cgi > 66008 nobody 1 40 178M 93000K accept 1 1:46 0.63% php-cgi > 69286 nobody 1 40 178M 92208K accept 1 0:37 0.63% php-cgi > 47289 nobody 1 40 73400K 70640K kqread 1 12:02 0.59% lighttpd > 65980 nobody 1 40 178M 93156K accept 1 1:51 0.59% php-cgi > 2008/11/7 Ivan Voras <[EMAIL PROTECTED]> > > >> Ken Chen wrote: >> >>> Oh.. sorry, I forgot to provide the information of my environment. >>> >>> web4# php-cgi -v >>> PHP 5.2.6 (cgi-fcgi) (built: Nov 2 2008 11:16:30) >>> Copyright (c) 1997-2008 The PHP Group >>> Zend Engine v2.2.0, Copyright (c) 1998-2008 Zend Technologies >>> with XCache v1.2.2, Copyright (c) 2005-2007, by mOo >>> web4# /usr/local/lighttpd/sbin/lighttpd -v >>> lighttpd-1.4.19 - a light and fast webserver >>> Build-Date: Sep 1 2008 16:58:51 >>> web4# uname -a >>> FreeBSD web4..com 7.0-RELEASE-p5 FreeBSD 7.0-RELEASE-p5 #11: Mon Nov >>> >> 3 >> >>> 01:10:36 CST 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/WEB4 i386 >>> web4# ps alx | grep php-cgi | grep -v grep | grep sbwait >>> 65534 57776 47240 0
Re: HELP DEBUG: FreeBSD 6.3-RELEASE-p3 TIMEOUT - WRITE_DMA + other strange behaviour!
Moring and have a nice week! The problems continues. It appears that this has somethind to do with the xl,fxp,atapci cards. On friday evening when I had hw access to the machine I've pulled out the power of one of the disks and remove rl0. The situation was absolutely the same! timeouts and timeouts again After seeing this isn't helping I've patched my kernel with http://freenas.svn.sourceforge.net/viewvc/freenas/branches/0.69/build/kernel-patches/ata/files/patch-ata.diff?view=markup this patch and tried increasing the timeout to 10 then to 15 then to 25 - nothing helped. I got crazy and pulled of my home movie station (PIII 1ghz, 384ram, via(I think chipser) - I'll post new dmesg here). I've moved the disks (only 4 of the as I wasn't using the fitfth) and plugged xl0, fxp0 and promise card in the new machine. It started just fine and seemed to work while I've started to get the *bad* timeouts again! F***!!! I saw that the timeout of the tunable sysctl is 5 and increased it to 15 but still on heavy (read mythtv scan about 300G media files and other stuff) and 3-4 fetches fetching online radios) ... so I think is has something to do with the promise card. Oh yes, I've also got Sep 28 21:32:47 azimud kernel: xl0: transmission error: 90 Sep 28 21:32:47 azimud kernel: xl0: tx underrun, increasing tx start threshold to 120 bytes because these problems drives me tooo mad! I simply want a working machine, I'm going to pull of the xl0 and promise card from this machine (use integrated ide controllers) and another fxp because seems that fbsd now has problems and with xl's (Which reminds me for the 4.X - it used to work perfectly with xls rls fxps... but that's another topic...anyways). If that doesn't help I'll be forced to migrate to linux :(... Because I'll have free machine with the problematic promise ultra133 controller and two disks in it, I can provide a serial console to this machine is anyone is interested in debugging this issue anyone? here are the new info: http://valqk.ath.cx/tmp/dmesg.new http://valqk.ath.cx/tmp/vmstat.new (oh I have no usbs connected to this machine [yet]). cheers, valqk. Anton - Valqk wrote: > Thanks Jeremy and Peter, > you are right that the machine has *lots* ot hardware in it, > I was thinking of the power supply as a reason and measured the 5 and 12 > volts - seemd to be ok 11.8 and 5.2 with all hardware in it. > The shared irq is the one I've thought of and that's why I've posted > vmstat -i to hear your opinion. > [forgot to mention that I've read the wiki and next step is to patch the > kernel with > http://freenas.svn.sourceforge.net/viewvc/freenas/branches/0.69/build/kernel-patches/ata/files/patch-ata.diff?view=markup > this patch (any bad words for this patch or could just run - nothing bad > can happen?)] > > Yes, I have 3 nics(2 on pci) + pci ide promise, I'll get a smart switch > with vlans and I'll leave just the integrated xl0 and fxp0 with both > external ips on it these days, > but first I'll patch the kernel if Jeremy says it won't hurt (as far as > I saw just a timeout is moved from hardcoded value to a sysctl?)... > I have another promise card that is a raid controller, but when I've > started loking for one I've asked here and there were answers for > PROMISE ULTRA ATA133 for being a good card for my freebsd ( > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=290848+0+archive/2008/freebsd-stable/20080316.freebsd-stable > ) > (hmm, just saw that Jeremy pointed out promise card: 'Their Ultra133 > TX2 card works fine on 33MHz PCI bus machines; don't worry about the > card being 66MHz, it will downthrottle correctly.') so maybe the problem > will be solved if I leave just two nics and no rl0... > Actually I'm using 6.3 here because I didn't wanted this to happen and I > was ware of such problems happening on 7-current > > So test must be done... pls just answer about the patch will it be > helpful or I should try: > > 1. remove rl0 and run only one isp for the test. > 2. replace the ultra 133 card with another one. > 3. try to replace the ATA100 cables (the one with 80 wires) with an > older ones with only 40 cabels? > 4. ? anything else? > > > Anton - Valqk wrote: > >> Hello, >> I have a VERY strange behaving 6-3p3 with DMA tmieouts and network cards >> 'dropping traffic'. >> Following is the explanation of hardware and the thinga that are happening. >> The machine is DELL optiplex PII 300mHZ with 512RAM. >> It has 3 NICs: >> fxp0: flags=8843 mtu 1500 >> options=8 >> inet 7.8.9.10 netmask 0xf000 broadcast 7.8.9.255 >> ether 00:91:21:16:14:bf >> media: Ethern
Re: HELP DEBUG: FreeBSD 6.3-RELEASE-p3 TIMEOUT - WRITE_DMA + other strange behaviour!
Thanks Jeremy and Peter, you are right that the machine has *lots* ot hardware in it, I was thinking of the power supply as a reason and measured the 5 and 12 volts - seemd to be ok 11.8 and 5.2 with all hardware in it. The shared irq is the one I've thought of and that's why I've posted vmstat -i to hear your opinion. [forgot to mention that I've read the wiki and next step is to patch the kernel with http://freenas.svn.sourceforge.net/viewvc/freenas/branches/0.69/build/kernel-patches/ata/files/patch-ata.diff?view=markup this patch (any bad words for this patch or could just run - nothing bad can happen?)] Yes, I have 3 nics(2 on pci) + pci ide promise, I'll get a smart switch with vlans and I'll leave just the integrated xl0 and fxp0 with both external ips on it these days, but first I'll patch the kernel if Jeremy says it won't hurt (as far as I saw just a timeout is moved from hardcoded value to a sysctl?)... I have another promise card that is a raid controller, but when I've started looking for one I've asked here and there were answers for PROMISE ULTRA ATA133 for being a good card for my freebsd ( http://docs.freebsd.org/cgi/getmsg.cgi?fetch=290848+0+archive/2008/freebsd-stable/20080316.freebsd-stable ) (hmm, just saw that Jeremy pointed out promise card: 'Their Ultra133 TX2 card works fine on 33MHz PCI bus machines; don't worry about the card being 66MHz, it will downthrottle correctly.') so maybe the problem will be solved if I leave just two nics and no rl0... Actually I'm using 6.3 here because I didn't wanted this to happen and I was ware of such problems happening on 7-current So test must be done... pls just answer about the patch will it be helpful or I should try: 1. remove rl0 and run only one isp for the test. 2. replace the ultra 133 card with another one. 3. try to replace the ATA100 cables (the one with 80 wires) with an older ones with only 40 cabels? 4. ? anything else? Anton - Valqk wrote: > Hello, > I have a VERY strange behaving 6-3p3 with DMA tmieouts and network cards > 'dropping traffic'. > Following is the explanation of hardware and the thinga that are happening. > The machine is DELL optiplex PII 300mHZ with 512RAM. > It has 3 NICs: > fxp0: flags=8843 mtu 1500 > options=8 > inet 7.8.9.10 netmask 0xf000 broadcast 7.8.9.255 > ether 00:91:21:16:14:bf > media: Ethernet autoselect (100baseTX ) > status: active > rl0: flags=8843 mtu 1500 > options=8 > inet 8.9.10.11 netmask 0xffe0 broadcast 8.9.10.255 > ether 00:02:44:73:2a:fa > media: Ethernet autoselect (100baseTX ) > status: active > xl0: flags=8843 mtu 1500 > options=9 > inet 192.168.123.2 netmask 0xff00 broadcast 192.168.123.255 > inet 192.168.123.5 netmask 0xff00 broadcast 192.168.123.255 > inet 192.168.123.6 netmask 0xff00 broadcast 192.168.123.255 > ether 00:c0:4f:20:66:a3 > media: Ethernet autoselect (100baseTX ) > status: active > fxp0 and rl0 are external links to the world and are plugged into pci slots > xl0 is the internal interface and is integrated on motherboard. > It also has 1 PROMISE ULTRA133 ATA pci IDE controller plugged into the > pci slot. > It has 5 disks in it - 4 connected to the PROMISE card and 1 to the > motherboard ide. > > they are as follows: > ad0 and ad6 are two identical hitachi disks in gmirror for the system > and a partition that I keep backups on. > > ad4, ad5 and ad7 are storage disks - seagates 500GB 8mb cache that I > keep isos etc files on and are the problematic (maybe because of high > traffic operations compared to the other two?). > > What is the problem: > Actually there are two problems: > 1. I get a lot of dma times outs. mostly on ad5 and ad7 where I keep > files over 4-5MBs and write/read very often with 3-6-8MB/s from the > disk. I don't use ad4 so I can not tell if there's gona be timeous but I > suppose there will (currently has linux partitions on it and is not > mounted). I get these errors: > dmesg.today:ad7: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=5554848 > dmesg.today:ad7: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=5914112 > dmesg.today:ad7: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=14924096 > dmesg.today:ad7: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=374303456 > dmesg.today:ad7: FAILURE - WRITE_DMA48 status=51 > error=10 LBA=374303456 > dmesg.today:g_vfs_done():ad7[WRITE(offset=191643369472, > length=131072)]error = 5 > dmesg.today:ad5: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=50757760 > dmesg.today:ad5: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=50760192 > dmesg.today:ad5: TIMEOUT - WRITE_DMA ret
HELP DEBUG: FreeBSD 6.3-RELEASE-p3 TIMEOUT - WRITE_DMA + other strange behaviour!
Hello, I have a VERY strange behaving 6-3p3 with DMA tmieouts and network cards 'dropping traffic'. Following is the explanation of hardware and the thinga that are happening. The machine is DELL optiplex PII 300mHZ with 512RAM. It has 3 NICs: fxp0: flags=8843 mtu 1500 options=8 inet 7.8.9.10 netmask 0xf000 broadcast 7.8.9.255 ether 00:91:21:16:14:bf media: Ethernet autoselect (100baseTX ) status: active rl0: flags=8843 mtu 1500 options=8 inet 8.9.10.11 netmask 0xffe0 broadcast 8.9.10.255 ether 00:02:44:73:2a:fa media: Ethernet autoselect (100baseTX ) status: active xl0: flags=8843 mtu 1500 options=9 inet 192.168.123.2 netmask 0xff00 broadcast 192.168.123.255 inet 192.168.123.5 netmask 0xff00 broadcast 192.168.123.255 inet 192.168.123.6 netmask 0xff00 broadcast 192.168.123.255 ether 00:c0:4f:20:66:a3 media: Ethernet autoselect (100baseTX ) status: active fxp0 and rl0 are external links to the world and are plugged into pci slots xl0 is the internal interface and is integrated on motherboard. It also has 1 PROMISE ULTRA133 ATA pci IDE controller plugged into the pci slot. It has 5 disks in it - 4 connected to the PROMISE card and 1 to the motherboard ide. they are as follows: ad0 and ad6 are two identical hitachi disks in gmirror for the system and a partition that I keep backups on. ad4, ad5 and ad7 are storage disks - seagates 500GB 8mb cache that I keep isos etc files on and are the problematic (maybe because of high traffic operations compared to the other two?). What is the problem: Actually there are two problems: 1. I get a lot of dma times outs. mostly on ad5 and ad7 where I keep files over 4-5MBs and write/read very often with 3-6-8MB/s from the disk. I don't use ad4 so I can not tell if there's gona be timeous but I suppose there will (currently has linux partitions on it and is not mounted). I get these errors: dmesg.today:ad7: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=5554848 dmesg.today:ad7: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=5914112 dmesg.today:ad7: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=14924096 dmesg.today:ad7: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=374303456 dmesg.today:ad7: FAILURE - WRITE_DMA48 status=51 error=10 LBA=374303456 dmesg.today:g_vfs_done():ad7[WRITE(offset=191643369472, length=131072)]error = 5 dmesg.today:ad5: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=50757760 dmesg.today:ad5: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=50760192 dmesg.today:ad5: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=12032 dmesg.today:ad5: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=50769792 strange thing is that I'm seeing the g_vfs_done just recently and this problem is from the very start of this hardware setup of the machine. The machine used to work with two hitachi disks connected to the ad0 and ad1 (integrated ide) and only one - xl0 - nic perfectly. The problems started when I plugged in the PROMISE and other nic cards and started using it as router, fileserver and backup server (each in separate jail, except the pf firewall). 2. The other strange issue is that when (I guess) it starts timeouting *sometimes* not everytime I'm loosing connection to xl0 or fxp0 (sometimes the rl0 works and accepts connections from the outside, sometimes - not). When I go to the machine and plug a monitor - there are no messages from kernel, no logs in /var/log/messages or debug - noting. Stange thing is that I ping host from the local net and it time outs, ifconfig shows that interface is connected at fd 100mbit and everyting seems ok. I've tried ifconfig xl0 down up but doesn't help, tried plugging out the cable and it got connected but not packets passed - timeout again! I've rebooted and nic came up. These 'drops' became more and more common recently and last night I wasn't able to login for about an hour and after that the machine came back up again by itself!!!that's in the lan - but it wasn't accessible at all from the outside - strange thins is that it replied to ping but I wasn't able to even open the ssh port connection and the nat wasn't working?! After that I've remembered that at this time I have a cronjob started for about an hour that fetches into a file a online radio cast for an hour wired!!! it also have rtorrent, apache22, samba (in a jail) runing. some output from it can be found here: http://valqk.ath.cx/tmp/dmesg http://valqk.ath.cx/tmp/vmstat http://valqk.ath.cx/tmp/smartctl please give any ideas/hints/solutions! thanks a lot to everyone! cheers, valqk. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Stable SATA pci card for FreeBSD 6.x/7.0
Hi, I'm interested and following the thread, can you pls send the communication that's of importance to all at the end? cheers, valqk. Jeremy Chadwick wrote: > On Tue, Aug 05, 2008 at 03:16:41PM +0200, Sebastiaan van Erk wrote: > >> Sorry for forgetting to paste the smart details. Pressed send too quickly. >> > > A note for the list: Sebastiaan and I are discussing the details > off-list. I don't know if he forgot to CC the list on his replies, or > if he intentionally sent them to me directly. :-) > > Just thought I'd make note of that here, in case readers wonder what > becomes of this issue. > > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: CLARITY re: challenge: end of life for 6.2 is prematurewithbuggy 6.3
Thanks for the answer, so lets tell what I think :) Marian Hettwer wrote: On Wed, 11 Jun 2008 18:50:57 +0300, Anton - Valqk <[EMAIL PROTECTED]> wrote: Thanks for the answer! I'm glad someone answered me a human way, because two times before, I wasn't answered that way (well... my posts were angry and incomplete but...that's why i didn't continued to post...my bad). Well then, lets continue answering in a human way. Which is, funnily enough, usually the more productive way too ;-) now on topic: yeah! Thats unfortunatly true. But there is a way around. As soon as you have several FreeBSD boxes, I'd advise you to install your own FreeBSD box for packages building. So if you need to update your php installations, go to your build box (which has the very same versions of programs installed as your production boxes), update your ports tree and do a "make package" of your new php port. If the new php package works fine on your build box, roll it out via "pkg_add -r $NEWPHPTHINGY" and off you go. I do have a build server(well a jail but works for me), also I have test eviornment (jailed too). I use this jail to build all my pkgs and use pkg_add -r (sweeet!!). For most of the ports this works, but sometimes something in make package breaks and i get a port installed partially (last case - apache22 got installed but no /usr/local/etc/rc.d/apache22 rc script, previous - pg_ctl never got installed) and in +CONTENTS file the missing files claimed to be there. hm... sounds like a bug to me. On the other hand, you have to try to get it to be reproducable. If it's a one timer then yes, it's annoying, but really really hard to reproduce and therefor to fix. the problem is that I don't have enought time to setup a testing server and find out when the problem occurs, because it's random seen, on 10-15th build of the new port this happens, I've noticed that if I make #> make deinstall distclean install pakcage-recursive the problem occurs much more rare compared to just #> make deinstall ditsclean package-recursive I simply currently don't have time for test setup ;( I've had to rebuild that kind of port so I can install it again (after pkg_delete) to have the port working. yeah, annoying. This happens most often when I do make install package-recursive (so I can get all needed ports installed). If you can reproduce it step by step, it may be worth posting to ports@ again with what you did and what happened. Either you're doing something wrong, or something is broken. However, it needs to be reproducable. At least in your environment. As a starter, so to say :) The more detailed your steps are written down, the more likely someone will either follow those steps or give you a direct hint on "humm, could be something bad over there... hm hm). I understand that, that's why I didn't posted again because, as I said i don't have time to sitdown and setup and try to reproduce it. Another strange thing is that when I use php-extensions to build all that I need (this takes most of my time when build/install new php) breaks because of the ?'bug'? described few lines above. as I said noone got interested in this problem... I can't say anything specific about the php problem you said. I'm not using php, or well, very rarely. I'll give it a try to update it the make package way next time. Unluckily this is a one-box only system. hmmm... If I find the time to test, I'll drop you mail. But time is rare (admin life vs. normal life). To cut that short: Yeah, I can understand that this is annoying. But I'm sure as hell: - if it's a bug it can be fixed - if it's a user error, it can be changed - and all this has happened to me when trying to build my own debian packages too ;) And it happened to me with Gentoo, too. Nothing new at all. Just the regular annoyances in sysadmins life. IMO :) agree with that, just my effort with debian is much smaller than fbsd ports. Another _very important_ thing is that there is no binary support to packages that has vulns, and you have to rebuild them from ports. Well, its one time doing a make package... Even debian has no plus point there (at least in our environment at work). We pretty much always need our Apache 2 custom build, not the way the Debian projects build it. Thus we have a Debian build box around and build our own Apache 2.2 package. This is, indeed, the same amount of effort you would have when using FreeBSD. IMO the overhead in Debian to build a package is higher than in FreeBSD, but YMMV. If you build packages from source then debian just sux (much more complex and long procedure), but there is a tell - "if you do it with debian - do it THE DEBIAN WAY"
Re: CLARITY re: challenge: end of life for 6.2 is premature with buggy 6.3
Robert Watson wrote: On Wed, 11 Jun 2008, Anton - Valqk wrote: I fully agree with the lines below. As noticed below there is more attention to developing new features, than making releases rock solid stable. ... Ah, another thing, I'm waiting for virtualization networking layer for jails for quite long. I've tested it on a test server, worked perfect, but on production I don't want to patch my base. there are few other features to jals that never got commited in base, and as I said I don't want to patch it... The reason that the virtualization patches aren't in the tree is precisely *because* we care about stability and are willing to slow down feature development in order to accomplish it. Some features take years to stabilize, and just because a patch works OK in your environment doesn't mean it will work in everyone's. Moderating the rate at which we adopt agressive new features is part of an intentional strategy to avoid letting development trees destabilize to a point where it's unproductive. I totally agree with that point, just commented that it's been year(s) since its appearence an maybe not enought effort in it (just an outsider thought, can't know if it is) and the fueature is a really really great and nice one! Robert N M Watson Computer Laboratory University of Cambridge ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: CLARITY re: challenge: end of life for 6.2 is premature withbuggy 6.3
Thanks for the answer! I'm glad someone answered me a human way, because two times before, I wasn't answered that way (well... my posts were angry and incomplete but...that's why i didn't continued to post...my bad). now on topic: Marian Hettwer wrote: Hi there, some thoughts to your problem in regards to Debian administration time needed vs. FreeBSD administration time needed. I believe I can make a point there, since I have 600 debian boxes under my hood but still am a FreeBSD advocate ;-) On Wed, 11 Jun 2008 12:53:02 +0300, Anton - Valqk <[EMAIL PROTECTED]> wrote: My main drama with FreeBSD is that ports don't have -SECURITY patches, and if I there is a bug in php I have to rerbuild and populate the latest version. Thats unfortunatly true. But there is a way around. As soon as you have several FreeBSD boxes, I'd advise you to install your own FreeBSD box for packages building. So if you need to update your php installations, go to your build box (which has the very same versions of programs installed as your production boxes), update your ports tree and do a "make package" of your new php port. If the new php package works fine on your build box, roll it out via "pkg_add -r $NEWPHPTHINGY" and off you go. I do have a build server(well a jail but works for me), also I have test eviornment (jailed too). I use this jail to build all my pkgs and use pkg_add -r (sweeet!!). For most of the ports this works, but sometimes something in make package breaks and i get a port installed partially (last case - apache22 got installed but no /usr/local/etc/rc.d/apache22 rc script, previous - pg_ctl never got installed) and in +CONTENTS file the missing files claimed to be there. I've had to rebuild that kind of port so I can install it again (after pkg_delete) to have the port working. This happens most often when I do make install package-recursive (so I can get all needed ports installed). I've tried to tell this in ports@ and I was answered that "everything is working for us" or kind of. no one tried to investigate... Another strange thing is that when I use php-extensions to build all that I need (this takes most of my time when build/install new php) breaks because of the ?'bug'? described few lines above. as I said noone got interested in this problem... I have another complain from fbsd but I'll tell about it at the end. Another _very important_ thing is that there is no binary support to packages that has vulns, and you have to rebuild them from ports. Well, its one time doing a make package... Even debian has no plus point there (at least in our environment at work). We pretty much always need our Apache 2 custom build, not the way the Debian projects build it. Thus we have a Debian build box around and build our own Apache 2.2 package. This is, indeed, the same amount of effort you would have when using FreeBSD. IMO the overhead in Debian to build a package is higher than in FreeBSD, but YMMV. If you build packages from source then debian just sux (much more complex and long procedure), but there is a tell - "if you do it with debian - do it THE DEBIAN WAY"... :-). I totally agree with that, but on all debian machines I use packages provided from debian, because they've made it very modular, and I was able to config them the way I need and everything is working for me. In 99.99% of the cases when I do apt-get dist-upgrade the machine works like a charm after it, and that's a fact (in fbsd when make installworld too, but not for ports - which is the focus here). Actually that's what *BSD prouds with - building everything from source (like gentoo), well it's a must to be simplified then (debian where everything is supposed to be used from bin .deb) :). About the bug fixes, I think if that's a SECURITY backport it shouldn't fix bugs, because I've saw few devs deploying an app and the were using 'known bug' in ruby to work with. so they were unable to use higher version of ruby that got this bug fixed. (we'll obviously a developer mistake in design but if it's in a production will take months to redesign - not an option). Which is why maybe it's better not to fix bugs but just vulns in SECURITY backports (according to me of course) - if you need that bug fixed, then install new version. Just a simple example: I have 4-5 fbsd machines and about 15-20 debian stable machines. To administer fbsd machines when there are ports bugs(bugs in ports I use) it takes me at least about 4times more time than update _all_ debian machines... depends on the way you go. Genereally speaking, you really really want a build and test machine before you deploy a security update or even a new version of your software (in this case: php). Even with Debian boxes you really shouldn't just "apt-g
Re: CLARITY re: challenge: end of life for 6.2 is premature with buggy 6.3
Just my 5cents (some thoughts), I fully agree with the lines below. As noticed below there is more attention to developing new features, than making releases rock solid stable. As mentioned in reply posts the 3 branches 6.X 7.X and 8.X takes too many resources and is very hard to support. I, personally, will be waiting for 7.2 release (noticed that .2 over few (3-4 years)) are most stable ones. My main drama with FreeBSD is that ports don't have -SECURITY patches, and if I there is a bug in php I have to rerbuild and populate the latest version. Another _very important_ thing is that there is no binary support to packages that has vulns, and you have to rebuild them from ports. Just a simple example: I have 4-5 fbsd machines and about 15-20 debian stable machines. To administer fbsd machines when there are ports bugs(bugs in ports I use) it takes me at least about 4times more time than update _all_ debian machines... Well...I have other things to do too, too many... now guess what I will choose? I'll use debian, and that's not because I don't have will to use freebsd, it's simply because I do my tasks 4 times slower than when I choose debian. Someone will say "FreeBSD is not for you, then back off". That's not the point, I like fbsd, but as more busy I get, as less I'll be able to use it, takes too much of my time. Once I've told that there is no binary support (but I didn't expressed myself correctly). There is no ports VULNS binary support. If there is (and I've never heard of it), I'll be very happy someone to point me out this, because I'll continue running fbsd. Ah, another thing, I'm waiting for virtualization networking layer for jails for quite long. I've tested it on a test server, worked perfect, but on production I don't want to patch my base. there are few other features to jals that never got commited in base, and as I said I don't want to patch it... in linux (debian for me) there is xen that works with 'new' intel hardware virtualization, that's another red point for debian there are other things that I'll leave unsaidso... that's all for now. sorry for my bad english, it's not my native. these are just my thoughts and don't want to force anyone to agree with them, but I'll be happy to read your thoughts on this. cheers, valqk. Andy Kosela wrote: On 6/8/08, Freddie Cash wrote: On 6/7/08, Jo Rhett wrote: The question I raised is simply: given the number of bugs opened and fixed since 6.3-RELEASE shipped, why is 6.3 the only supported version? Why does it make sense for FreeBSD to stop supporting a stable version and force people to choose between two different unstable versions? Is this really the right thing to do? Define the terms "stable" and "unstable", how you measure said "stability" and "instability", and what you are comparing them against. This whole discussion is really interesting as it clearly showcases two common trends in computing (rapid development vs stability) On the one side we got people (let's call them developers or computer scientists) who are more interested in development than stabilization of the existing code base. It's natural for them to think more about new features, researching new ideas and implementing them. It resembles an academic project, research project.Those computer scientists do not care much about stability, they are mainly interested in hacking on the code for the fun of it. It is open source after all as someone wisely remarked. From my own experience most if not all community based projects are more interested in following this trend than stabilization of the code. Although they do care about stability of their code base, their focus is more on implementing new features and moving rapidly forward. In today's quickly changing world we see this trend as prevailing. On the other hand though, there is a trend which focuses on maximum long term stabilization of the code base. Usually we see this trend in high end commercial companies serving the needs of mission critical businesses where even a minute of downtime can cause loss of thousands of dollars or even loss of lives of people (imagine stock exchanges, banks, financial & insurance institutions, army and police facilities, hospitals, nuclear plants etc.). Those types of businesses/institutions truly needs a maximum stable operating system. They really do not care about "new features", but they do care about maximum stability of the existing code, security, and nonstop business continuity even in the face of natural disasters. There is only one operating system I know of that survived 9/11 attacks - this is OpenVMS. It's not uncommon to see VMS uptimes of more than 10 years (you can ask Amsterdam police for evidence). Now that is a true stability! On the other note though, stability is the direct opposition of development and change. Something which is *stable* cannot change or must change very slowly in the long term. On the othe
nscd strange behaviour
Hi there group, I have nscd running on 6.3 with backports patches, but maybe this will apply to the 7.0? What's the problem: i have nss setup with nss_pg module and authenticates passing through pam pg module. I have nscd running so I can make fewer queries to the pg server when system retrieves uid<->userid. But when I change the password in pg database, I can't get authenticated on the machine running nscd. When I restart it, the new password is retrieved as it should be and authentication goes ok. my config is: moser# cat /etc/nscd.conf # # Default caching daemon configuration file # $FreeBSD: src/etc/nscd.conf,v 1.2.2.1 2007/10/19 00:09:54 bushman Exp $ # enable-cache passwd yes enable-cache group yes enable-cache hosts no enable-cache services no enable-cache protocols no enable-cache rpc no enable-cache networks no #custom threads 25 So my question: Is this a suggested behaviour and shouldn't nscd cache all in passwd struct but password itself? any suggestions, opinions and comments are welcome! cheers, valqk. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: why does my apache-worker broke after upgrade to 6_3_RELEASE?
well, well, well. FreeBSD Errata Notice FreeBSD-EN-08:01.libpthread is this connected to my problem with apache2-worker? I think so. another problem in last two months. I'm experiencing another strange problem with mount_nullfs locking. The system is simply, hanging, despite of losing dirs that are null mounted! IMHO FreeBSD is going very wrong way... in 4.10, 5.X times the sysadmin wasn't working when he got his job done. now you simply can't know what will happen on next update to 'STABLE' and no bin packages (unlike debian). If this continues, it won't take me long to migrate to debian, despite I don't want to, but I want to have a nice deep sleep, no alarms in the middle of the night cheers, valqk. Aryeh M. Friedman wrote: > Anton - Valqk wrote: >> Hi group, >> does anyone has idea >> why the [EMAIL PROTECTED] upgrade to latest 6_3_RELEASE >> broke my apache-worker?!??? >> In logs I get: >> Fatal error 'kse_exit() failed for system scope thread' at line 1215 in >> file /usr/src/lib/libpthread/thread/thr_kern.c (errno = 22) >> >> I don't think it's a suggested behavior? >> This broke my apache for christ sake!!! >> Not pretty sure about all other threaded apps. >> after 10 times I've rebuilded my port from scratch and seeing that it's >> not a problem with this, >> I've found a solution: >> adding in /etc/libmap.conf >> >> [httpd] >> libpthread.so.2 libthr.so.2 >> libpthread.so libthr.so >> >> >> but can anyone tell me why the @[EMAIL PROTECTED]@[EMAIL PROTECTED]@$#% I >> get to this state >> by only updating to 6_3_RELEASE which is SUPPOSED TO BE ROCK SOLID >> STABLE >> and don't break that ugly things!!! >> freebsd is really pissing me off recently! >> I'm seeing a great increase of the problems recent years, as I'm >> following the list and dealing with it. >> anywayz, can anyone answer me plz why did I get to this state? >> >> thanks >> >> >> > Did you re-install apache from ports and everything it depends on? > If so look at the man page for libmap.conf (*BUT* make extra sure you > actually re-installed everything instead of just thinking you did) > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Jail crontab crashing?
I've found the actual line from which the cron was crashing. By mistake I've uncommented: #1,31 0-5 * * * rootadjkerntz -a and that's in a jail enviornment, when I commented it again the cron started working as expected. I agree that it's stupid ti call this command when in jail, because jail don't have perms to touch system time, but is this behaviour of the cron a suggested one? cron to die if it calls this? I don't think so? what would you say? Anton - Valqk wrote: Hi there, have anyone faced a cron crashing in a jail when changing the /etc/crontab? I'm running a jail with nsswitch using pgsql backend and I've noticed a strange behaviour of my crontab. Every time I change the /etc/crontab file I get (or make crontab -e and save it) /usr/sbin/cron[32864]: (*system*) RELOAD (/etc/crontab) in /var/log/cron and immediately after that the cron dies with a core (core file is in /var/cron/cron.core), I've made a ktrace but nothing strange can be seen in it, heres the link to the kdump file: http://valqk.ath.cx/ktrace.out.txt any ideas appriciated! cheers, valqk. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Jail crontab crashing?
We've found the problem with a friend of mine. /etc/crontab has wrong syntax in defining crons - I've used spaces instead of tab between the * * * * * and the username really my bad, maybe copied the string from the other machine it was running on and pasted without cheching but... I don't think it's normal an incorrect crontb syntax to crash the crontab with coredump? is it? the other strange thing, the line below the incorrect syntax there is a line with a correct one, that wasn't working too, and even if the cron don't core, the correct line wasn't working maybe the cron stops parsing if see incorrect line? is this a suggested behaviour? maybe it's a bug, along with the crashing with core when no tab used between the * * * * * and the user... dunno, pls someone that's familiar to tell... 10x! :-) Anton - Valqk wrote: Hi there, have anyone faced a cron crashing in a jail when changing the /etc/crontab? I'm running a jail with nsswitch using pgsql backend and I've noticed a strange behaviour of my crontab. Every time I change the /etc/crontab file I get (or make crontab -e and save it) /usr/sbin/cron[32864]: (*system*) RELOAD (/etc/crontab) in /var/log/cron and immediately after that the cron dies with a core (core file is in /var/cron/cron.core), I've made a ktrace but nothing strange can be seen in it, heres the link to the kdump file: http://valqk.ath.cx/ktrace.out.txt any ideas appriciated! cheers, valqk. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Jail crontab crashing?
Thanks for the answer, I've never responded because I have no time to test recompiling _all_ libs and apache from scratch. When I do it I'll respond. I'm using worker because I prefer the new threaded apache model (also I'm unsg a fastcgid and I think it's working better with the worker, never benchmarked). I've done a rebuild of the world 6.3 because I put the nscd backport patch. (though I didn't moved to 7 yet, I'm waiting for 7.3 to come out). There were only 3 files changed when I cvsup-ed 6_3 and the patch changed some other. You are right about the pthread - just didn't saw that it dies again. I'll dig some more around and post if I find something. thanks! if anyone comes up with ideas, please respond. cheers, valqk. Jeremy Chadwick wrote: On Wed, Apr 02, 2008 at 12:25:57PM +0300, Anton - Valqk wrote: ok, just made a break trough, when I added cron to /etc/libmap.conf (here is my libnap.conf: user# cat /etc/libmap.conf [httpd] libpthread.so.2 libthr.so.2 libpthread.so libthr.so [cron] libpthread.so.2 libthr.so.2 libpthread.so libthr.so ) cron stopped crashing. cron isn't a threaded application, so I don't see how this fixed anything. cron doesn't link to any threaded libraries either. Use ldd and see for yourself. I've wrote an angry mail at sunday morning (GMT+2) about apache crashing (apache-worker) after a buildworld (by ezjail-admin), and added the above lines fixed my problem. And you didn't respond to the people who offered to help: http://lists.freebsd.org/pipermail/freebsd-stable/2008-March/041601.html You also didn't provide any details about what you upgraded from/to, or any other information. Chances are you did not rebuild all of your ports when upgrading the OS. The threading libraries change periodically, but do not necessarily change in library revision number (E.g. so.5 --> so.6). Also, why must you run Apache with the worker MPM? I've personally (meaning I'm talking about my experiences, not a general statement) never seen threaded Apache work -- only prefork. By the way, your ktrace isn't going to help much, because I don't think you ran ktrace with the correct arguments. I see a lot of fork() action, which is expected (because that's what cron does!), but no information about the children. You'd be better off using gdb on the coredump and cron, and figuring out where things crashed. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Jail crontab crashing?
ok, just made a break trough, when I added cron to /etc/libmap.conf (here is my libnap.conf: user# cat /etc/libmap.conf [httpd] libpthread.so.2 libthr.so.2 libpthread.so libthr.so [cron] libpthread.so.2 libthr.so.2 libpthread.so libthr.so ) cron stopped crashing. I've wrote an angry mail at sunday morning (GMT+2) about apache crashing (apache-worker) after a buildworld (by ezjail-admin), and added the above lines fixed my problem. Seems like I'm having a problem with libpthread but I don't know exaclty what. pls anyone help me, I have no idea why all apps using libpthread are crashing after the upgrade. This is only in the jail! in real system everything works as expected. pls help with ideas and tips! thanks. Anton - Valqk wrote: Hi there, have anyone faced a cron crashing in a jail when changing the /etc/crontab? I'm running a jail with nsswitch using pgsql backend and I've noticed a strange behaviour of my crontab. Every time I change the /etc/crontab file I get (or make crontab -e and save it) /usr/sbin/cron[32864]: (*system*) RELOAD (/etc/crontab) in /var/log/cron and immediately after that the cron dies with a core (core file is in /var/cron/cron.core), I've made a ktrace but nothing strange can be seen in it, heres the link to the kdump file: http://valqk.ath.cx/ktrace.out.txt any ideas appriciated! cheers, valqk. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Jail crontab crashing?
Hi there, have anyone faced a cron crashing in a jail when changing the /etc/crontab? I'm running a jail with nsswitch using pgsql backend and I've noticed a strange behaviour of my crontab. Every time I change the /etc/crontab file I get (or make crontab -e and save it) /usr/sbin/cron[32864]: (*system*) RELOAD (/etc/crontab) in /var/log/cron and immediately after that the cron dies with a core (core file is in /var/cron/cron.core), I've made a ktrace but nothing strange can be seen in it, heres the link to the kdump file: http://valqk.ath.cx/ktrace.out.txt any ideas appriciated! cheers, valqk. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: nscd 6 backport mirror
Just for the record - the backport patch works like a charm on 6_3 stable branch! Thanks a lot Denis!!! cheers, valqk. Anton - Valqk wrote: Here is the mirror of the backport for 6 that Denis sent me: http://valqk.ath.cx/nscd_fbsd_6/ Adam McDougall wrote: According to Denis Barov <[EMAIL PROTECTED]>: Gzipped patch avialable at http://www.dindin.ru/wiki/FreeBSD?action=AttachFile&do=get&target=nscd_backport.gz (78Kb) Mon, Dec 24, 2007 at 12:15 +0300 Denis Barov: Hi, Michael! In attachment patch for backporing nscd from RELENG_7 to RELENG_6. Tested on FreeBSD sepulca.yandex.ru 6.3-PRERELEASE FreeBSD 6.3-PRERELEASE #0: Thu Dec 23 22:06:36 MSK 2007 [EMAIL PROTECTED]:/usr/obj/usr/RELENG_6_ncsd/src/sys/GENERIC amd64 and works fine. Must I prepare pr? P.S. Don't forget to mkdir -p src/usr.sbin/nscd/agents before patching ;) On Wed, Jan 23, 2008 at 11:52:21AM +0200, Anton - Valqk wrote: Is there nscd/cached for STABLE 6 branch or it's only implemented in 7.X? Adam McDougall wrote: > I wanted to say Thanks!!! for this example, because before this point > I was under the impression that nscd/cached was of no use for NIS clients, > only LDAP or maybe other directory systems that I don't use. I tried > "cache compat" as below for passwd and group and it works! Our NIS > entries at work are big enough that without the cache, top takes 7+ seconds to > open, ssh login takes a few seconds, and samba logins were concerningly > slow. I did not try samba connections, but the other methods are much > faster now on the second run. Wanted to post this for the archive too. > > On Sat, Jan 19, 2008 at 02:17:11PM +0300, Michael Bushkov wrote: > > Hi Denis, > Several things: > 1. You definitely can't use cache for *_compat sources. I mean lines like > "group_compat: cache nis" aren't supported. > 2. Cache should work ok with the configuration you've mentioned in your > first example, i.e.: "group: cache compat". Just checking - why do you > think that cache isn't working? The correct way to determine it is to > perform the same query twice. During the first pass (when query is not > cached), the request will be processed by NIS module and you'll have all > the NIS-related stuff in the logs. On the second pass the request should be > handled by scd module - and you shouldn't see any activity in NIS logs. It > would be great to see the debug log (with nscd log turned on) separately - > for the first and the second pass. It would help to find the error in nscd, > if there is one. > > With best regards, > Michael Bushkov > > On Jan 17, 2008, at 9:55 PM, Denis Barov wrote: > > >>> Hello! >>> >>> I found some strange behaviour of NIS/nscd when NIS in compat mode. In >>> /etc/nsswitch.conf I have: >>> >>> netgroup: cache compat >>> passwd: cache compat >>> group:cache compat >>> > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
why does my apache-worker broke after upgrade to 6_3_RELEASE?
Hi group, does anyone has idea why the [EMAIL PROTECTED] upgrade to latest 6_3_RELEASE broke my apache-worker?!??? In logs I get: Fatal error 'kse_exit() failed for system scope thread' at line 1215 in file /usr/src/lib/libpthread/thread/thr_kern.c (errno = 22) I don't think it's a suggested behavior? This broke my apache for christ sake!!! Not pretty sure about all other threaded apps. after 10 times I've rebuilded my port from scratch and seeing that it's not a problem with this, I've found a solution: adding in /etc/libmap.conf [httpd] libpthread.so.2 libthr.so.2 libpthread.so libthr.so but can anyone tell me why the @[EMAIL PROTECTED]@[EMAIL PROTECTED]@$#% I get to this state by only updating to 6_3_RELEASE which is SUPPOSED TO BE ROCK SOLID STABLE and don't break that ugly things!!! freebsd is really pissing me off recently! I'm seeing a great increase of the problems recent years, as I'm following the list and dealing with it. anywayz, can anyone answer me plz why did I get to this state? thanks -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: nscd 6 backport mirror
Here is the mirror of the backport for 6 that Denis sent me: http://valqk.ath.cx/nscd_fbsd_6/ Adam McDougall wrote: According to Denis Barov <[EMAIL PROTECTED]>: Gzipped patch avialable at http://www.dindin.ru/wiki/FreeBSD?action=AttachFile&do=get&target=nscd_backport.gz (78Kb) Mon, Dec 24, 2007 at 12:15 +0300 Denis Barov: Hi, Michael! In attachment patch for backporing nscd from RELENG_7 to RELENG_6. Tested on FreeBSD sepulca.yandex.ru 6.3-PRERELEASE FreeBSD 6.3-PRERELEASE #0: Thu Dec 23 22:06:36 MSK 2007 [EMAIL PROTECTED]:/usr/obj/usr/RELENG_6_ncsd/src/sys/GENERIC amd64 and works fine. Must I prepare pr? P.S. Don't forget to mkdir -p src/usr.sbin/nscd/agents before patching ;) On Wed, Jan 23, 2008 at 11:52:21AM +0200, Anton - Valqk wrote: Is there nscd/cached for STABLE 6 branch or it's only implemented in 7.X? Adam McDougall wrote: > I wanted to say Thanks!!! for this example, because before this point > I was under the impression that nscd/cached was of no use for NIS clients, > only LDAP or maybe other directory systems that I don't use. I tried > "cache compat" as below for passwd and group and it works! Our NIS > entries at work are big enough that without the cache, top takes 7+ seconds to > open, ssh login takes a few seconds, and samba logins were concerningly > slow. I did not try samba connections, but the other methods are much > faster now on the second run. Wanted to post this for the archive too. > > On Sat, Jan 19, 2008 at 02:17:11PM +0300, Michael Bushkov wrote: > > Hi Denis, > Several things: > 1. You definitely can't use cache for *_compat sources. I mean lines like > "group_compat: cache nis" aren't supported. > 2. Cache should work ok with the configuration you've mentioned in your > first example, i.e.: "group: cache compat". Just checking - why do you > think that cache isn't working? The correct way to determine it is to > perform the same query twice. During the first pass (when query is not > cached), the request will be processed by NIS module and you'll have all > the NIS-related stuff in the logs. On the second pass the request should be > handled by scd module - and you shouldn't see any activity in NIS logs. It > would be great to see the debug log (with nscd log turned on) separately - > for the first and the second pass. It would help to find the error in nscd, > if there is one. > > With best regards, > Michael Bushkov > > On Jan 17, 2008, at 9:55 PM, Denis Barov wrote: > > >>> Hello! >>> >>> I found some strange behaviour of NIS/nscd when NIS in compat mode. In >>> /etc/nsswitch.conf I have: >>> >>> netgroup: cache compat >>> passwd: cache compat >>> group:cache compat >>> > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
REPOST for archive: Re: nscd again (nis client cache) patch for 6 stable branch
I've been searching in the mailist archives and never found this, so I'm reposting for archiving purposes. According to Denis Barov <[EMAIL PROTECTED]>: Gzipped patch avialable at http://www.dindin.ru/wiki/FreeBSD?action=AttachFile&do=get&target=nscd_backport.gz (78Kb) Mon, Dec 24, 2007 at 12:15 +0300 Denis Barov: > Hi, Michael! > In attachment patch for backporing nscd from RELENG_7 to RELENG_6. Tested on > > FreeBSD sepulca.yandex.ru 6.3-PRERELEASE FreeBSD 6.3-PRERELEASE #0: Thu Dec > 23 22:06:36 MSK 2007 > [EMAIL PROTECTED]:/usr/obj/usr/RELENG_6_ncsd/src/sys/GENERIC amd64 > > and works fine. > > Must I prepare pr? > > P.S. Don't forget to mkdir -p src/usr.sbin/nscd/agents before patching ;) On Wed, Jan 23, 2008 at 11:52:21AM +0200, Anton - Valqk wrote: Is there nscd/cached for STABLE 6 branch or it's only implemented in 7.X? Adam McDougall wrote: > I wanted to say Thanks!!! for this example, because before this point > I was under the impression that nscd/cached was of no use for NIS clients, > only LDAP or maybe other directory systems that I don't use. I tried > "cache compat" as below for passwd and group and it works! Our NIS > entries at work are big enough that without the cache, top takes 7+ seconds to > open, ssh login takes a few seconds, and samba logins were concerningly > slow. I did not try samba connections, but the other methods are much > faster now on the second run. Wanted to post this for the archive too. > > On Sat, Jan 19, 2008 at 02:17:11PM +0300, Michael Bushkov wrote: > > Hi Denis, > Several things: > 1. You definitely can't use cache for *_compat sources. I mean lines like > "group_compat: cache nis" aren't supported. > 2. Cache should work ok with the configuration you've mentioned in your > first example, i.e.: "group: cache compat". Just checking - why do you > think that cache isn't working? The correct way to determine it is to > perform the same query twice. During the first pass (when query is not > cached), the request will be processed by NIS module and you'll have all > the NIS-related stuff in the logs. On the second pass the request should be > handled by scd module - and you shouldn't see any activity in NIS logs. It > would be great to see the debug log (with nscd log turned on) separately - > for the first and the second pass. It would help to find the error in nscd, > if there is one. > > With best regards, > Michael Bushkov > > On Jan 17, 2008, at 9:55 PM, Denis Barov wrote: > > >>> Hello! >>> >>> I found some strange behaviour of NIS/nscd when NIS in compat mode. In >>> /etc/nsswitch.conf I have: >>> >>> netgroup: cache compat >>> passwd: cache compat >>> group:cache compat >>> > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: LD_LIBRARY_PATH in chroot?
Reply to myself, I've found the problem, you _must_ copy the ld.so.hints in /var/run/ to the /var/run/ chrooted dir. now everything works like a charm. Anton - Valqk wrote: Hi group, I'm setting up a chrooted enviornment and all my executables won't find libs in /usr/local/lib/ I've copied the /lib/ /bin/ /etc/ /usr/* and /usr/local/* in /chroot/env/ I'm chrooting in /choot/env/ and all my bin's can't find libs in /usr/local/lib if I do echo $LD_LIBRARY_PATH there is no env. why's that? any ideas? -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
LD_LIBRARY_PATH in chroot?
Hi group, I'm setting up a chrooted enviornment and all my executables won't find libs in /usr/local/lib/ I've copied the /lib/ /bin/ /etc/ /usr/* and /usr/local/* in /chroot/env/ I'm chrooting in /choot/env/ and all my bin's can't find libs in /usr/local/lib if I do echo $LD_LIBRARY_PATH there is no env. why's that? any ideas? -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Help choosing a good PCI PIDE controller
Hi there group, I have a P 233MHZ machine running as rouer, I have attached a second drive for a storage but the IDE controller on the mother board is very old and slow (UDMA33). The disk is new and have 16MB cache, but the IDE is very slow and have very bad performace - about 1.3MB/s. I want to attach a PCI PATA IDE controller (I'm running 6.3) that will be rock solid. can you please recommend me a good card? Thank you! cheers, Anton. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
nscd for STABLE_6_3?
Hi there, is there a nscd or something similar to nscd (cached) for the current STABLE_6_3? I'm interested in caching nsswitch (pgsql) queries so I can stop overloading the pg server. any ideas/experience? Cheers, valqk. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: jlogin.sh - a small nice jails helper!
Hi there,
your script didn't had what I wanted for the ps, that's why I wrote
simpler one for myself,
that's do the job for me - finds a string from ps axu from any jail :)
here it is, hopes it's useful (quick 15mins hack script).
#!/bin/sh
#list all jails processes
#$1 - jid - jail pattern || ALL
#$2 - string in jail ps axu cmd
if [ -n "$2" ]; then
psFilter="grep $2"
fi
if [ -n "$1" ] && [ "$1" != "ALL" ]; then
jName=$1
jID=`jls | grep $jName|awk '{print $1}'`
jRealName=`jls |grep $jName|awk '{print $3}'`
echo "Listing processes for $jRealName ( $jID )..."
if [ -n "$psFilter" ]; then
jexec $jID ps axu|$psFilter
else
jexec $jID ps axu
fi
else
for jID in `jls|awk '{print $1}'`;
do
if [ "$jID" -gt 0 ]; then
jRealName=`jls|grep $jID|awk '{print $3}'`
echo "Listing processes for $jRealName ( $jID )..."
if [ -n "$psFilter" ]; then
jexec $jID ps axu|$psFilter
else
jexec $jID ps axu
fi
fi
done
fi
Oliver Fromme wrote:
> Miroslav Lachman wrote:
> > It is nice idea, but I think you should have a better scripting style ;)
>
> Yes, it almost looked like perl. :-)
> May I suggest a few further improvements?
>
> > login_shell="/bin/tcsh"
>
> I certainly wouldn't want tcsh. How about looking at
> $SHELL, and if it doesn't exist, then fall back to the
> standard shell (which is /bin/sh).
>
> Also, the last command (jexec) should be preceded by
> "exec" so the shell doesn't hang around. So the last
> part of the script would look like this:
>
> jail_path=$(jls | awk '$1=='$jail_id' {print $4}')
>
> if [ -z "$SHELL" -o ! -x "$jail_path/$SHELL" ]; then
> login_shell="$SHELL"
> else
> login_shell="/bin/sh"
> fi
>
> echo "Logging in to $jail_hostname"
> exec jexec $jail_id $login_shell
>
> Best regards
>Oliver
>
> PS: By the way, here's another useful script that displays
> processes running in jails, ordered by jail IDs:
>
> http://www.secnetix.de/~olli/scripts/jps
>
>
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
jlogin.sh - a small nice jails helper!
Because I'm lazy and love the scripts, I wrote a nice small script that
matches a jailname and do a jexec JAILPID SHELL
so I can login fast to my jails.
According to me, there should be such tool!
Hopes something like this goes to STABLE!
here it is
#!/bin/sh
loginSHELL="/bin/tcsh"
[ -z "$1" ] && echo "No jail specified." && exit 1;
jName=$1;
jID=`jls | awk '{print $1,$3}'|grep $jName|awk '{print $1}'`
jRealName=`jls | awk '{print $1,$3}'|grep $jName|awk '{print $2}'`
[ -z "$jID" ] && echo "No such jail name $jName!" && exit 1;
echo "Logging in to $jRealName"
jexec $jID $loginSHELL
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
mount_nullfs in jail?
Hi Guys, Is there any way to have mount_nullfs working inside the jail? Please gime me any idea on that topic. Thank you. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: netstat -ni - A lot of collisions...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Well, the card is connected to a switch that is manageble and the port is set to 10Mbit Full duplex on purpose. I'm not setting the port speed manual - is that a problem when the port is not 100mbit/fd? This is the ifconfig output: fxp0: flags=18843 mtu 1500 options=48 inet 112.15.128.88 netmask 0xff00 broadcast 112.15.128.255 inet6 fe80::208:c7ff:fe5b:54f2%fxp0 prefixlen 64 scopeid 0x2 ether 00:08:c7:5b:54:a5 media: Ethernet autoselect (10baseT/UTP) status: active -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFTwENzpU6eaWiiWgRAjwgAJ4rfWbA5xDWmHE1MxWn36j2Njs/swCbBzJM Hg+zdfQGMra50Rh7k290Ofw= =DtBT -END PGP SIGNATURE- -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
netstat -ni - A lot of collisions...
Hi there group. I'm having trouble with a fxp0 card. When I ping it there are little lost packets, also the netstat -ni shows a lot collisions. The polling is enabled: kern.polling.idlepoll_sleeping: 1 kern.polling.stalled: 422 kern.polling.suspect: 937141 kern.polling.phase: 0 kern.polling.enable: 1 kern.polling.handlers: 1 kern.polling.residual_burst: 0 kern.polling.pending_polls: 0 kern.polling.lost_polls: 944349 kern.polling.short_ticks: 623 kern.polling.reg_frac: 20 kern.polling.user_frac: 50 kern.polling.poll_in_trap: 0 kern.polling.idle_poll: 0 kern.polling.burst_max: 150 kern.polling.each_burst: 5 kern.polling.burst: 150 hw.acpi.thermal.polling_rate: 10 What are they for? I've taken a look at the man netstat but wasn't able to find description? thanks! Here is the netstat -ni netstat -ni NameMtu Network Address Ipkts IerrsOpkts Oerrs Coll fxp0 1500 00:08:c7:5b:53:5f 4504986 0 2093233 0 185206 fxp0 1500 112.15.128112.15.128.88 1716322 - 2108533 - - plip0 15000 00 0 0 pflog 332080 00 0 0 lo0 16384 4157762 0 4157762 0 0 lo0 16384 127 127.0.0.1 3964179 - 3964179 - - lo0 16384 ::1/128 ::1 191850 - 191850 - - lo0 16384 fe80:5::1/64 fe80:5::10 -0 - - -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ipstealth question.
You are absolutely right but stealth is a strictly so, I you don't want a ttl change simply don't set net.inet.ip.stealth=1 I was just wondering... Joerg Pernfuss wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, 24 Sep 2006 14:06:49 +0300 Anton - Valqk <[EMAIL PROTECTED]> wrote: Hi group, I was wondering is option options IPSTEALTH not in the GENERIC on purpose? Without knowing the exact number, I am sure not decrementing the TTL violates at least one RFC. Imagine some datacenter with lots of FreeBSD installations and IPSTEALTH part of GENERIC. Ideally they do their routing via FreeBSD/netgraph too. Packets won't die, especially if they have a loop somewhere. Joerg - -- | /"\ ASCII ribbon | GnuPG Key ID | e86d b753 3deb e749 6c3a | | \ / campaign against |0xbbcaad24 | 5706 1f7d 6cfd bbca ad24 | | XHTML in email |.the next sentence is true. | | / \ and news | .the previous sentence was a lie.| -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFFFmmOH31s/bvKrSQRAoPAAJ4wod2pT6Irr8AzhF7M4LRaXJZ7TwCdGwQi y0kNNpGp0xG96o11YxfE2a8= =MXk6 -END PGP SIGNATURE- !DSPAM:45166995563711581215491! -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ipstealth question.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi group, I was wondering is option options IPSTEALTH not in the GENERIC on purpose. On some routers it's not possible to compile kernels, and you have to compile it before/after you got the router installed. Just wondering... -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFFmbJzpU6eaWiiWgRAthbAJ4509Yj4DRhBHHHkWZnGO6RwJo/JACeOBnM VQPWKnFBdRG6cpMpgaLIV9o= =WNdA -END PGP SIGNATURE- -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
if_ndis values setting problem.
Hello there, I have problem setting params to the if_ndis card. I'm using asus wl138g which is marvel chipset card. I've compiled the driver using ndisgen and the dmesg says the card is ok. When I try to do ifconfig ndis0 ssid SESS etc (with wep 128bit encryption) the led on the card blinks for a second and after that nothing happens. The ssid is empty, the encryption is WEP and all the values seems to be ok. #>ifconfig ndis0 ssid MYSESS nwkey ...key here... mode shared Any ideas how ot fix that? I'm using fbsd-stable. 10x in advance! -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
if_ndis values setting problem.
Hello there, I have problem setting params to the if_ndis card. I'm using asus wl138g which is marvel chipset card. I've compiled the driver using ndisgen and the dmesg says the card is ok. When I try to do ifconfig ndis0 ssid SESS etc (with wep 128bit encryption) the led on the card blinks for a second and after that nothing happens. The ssid is empty, the encryption is WEP and all the values seems to be ok. #>ifconfig ndis0 ssid MYSESS nwkey ...key here... mode shared Any ideas how ot fix that? I'm using fbsd-stable. 10x in advance! -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
