Re: bash versus sh test builtin
In the last episode (Jan 11), Jeffrey Goldberg said: > The -ne operator for [ in /bin/sh doesn't seem to work as in bash. > Also the bash behavior here is what matches /bin/[ most closely. > > $ /bin/sh > $ if [ $UID -ne 0 ] ; then > > echo not root > > fi > [: -ne: unexpected operator > $ exit > $ echo $SHELL > /usr/local/bin/bash > [jeff...@dobby ~/src/mount-rsnap]$ if [ $UID -ne 0 ] ; then > > echo not root > > fi > not root > > Does anyone have a recommendation of how to run this simple test in / > bin/sh and how to write tests reasonably portably? UID=$(id -u) if [ $UID -ne 0 ] ; then echo not root fi UID is not a variable set by /bin/sh, which is why the test fails. http://www.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_05_03 -- Dan Nelson dnel...@allantgroup.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
bash versus sh test builtin
The -ne operator for [ in /bin/sh doesn't seem to work as in bash. Also the bash behavior here is what matches /bin/[ most closely. $ /bin/sh $ if [ $UID -ne 0 ] ; then > echo not root > fi [: -ne: unexpected operator $ exit $ echo $SHELL /usr/local/bin/bash [jeff...@dobby ~/src/mount-rsnap]$ if [ $UID -ne 0 ] ; then > echo not root > fi not root Does anyone have a recommendation of how to run this simple test in / bin/sh and how to write tests reasonably portably? -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: schedule the test
Gustavo Millani wrote: Hi, Where can I schedule the test for certification? I found the site of Prometric and Vue. Have a look here: http://www.bsdcertification.org/ -- Glen Barber ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
schedule the test
Hi, Where can I schedule the test for certification? I found the site of Prometric and Vue. Gustavo Millani Brazil, Porto Alegre Veja quais são os assuntos do momento no Yahoo! +Buscados http://br.maisbuscados.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Speed Test in PC5750 verizon card
Hello, I use PC5750 verizon air card in FreeBSD 6.3 with ugencom device driver. It works fine but I only get 240Kbps upload and download speed even I got EDVO connection. When I test it in Windows, I got 1.4Mbps for download and 750Kbps for upload speed. I try so many staff and search but I couldn't find a solution. If anyone has similar experience then share with me. Thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Could not lock the file "/var/tmp/gconf-test-locking-file-blah"
Hello, I've installed FreeBSD 7.0-RELEASE #0 on an Acer Aspire 5100 laptop, and Gnome errors out when I try to start it. The kernel was compiled with no ehci support in order to get the laptop to not freeze on shutdown after syncing the disks, but there are no other major changes. I've installed gnome and all other packages from packages-7-stable/Lastest on the website, and it gives me the error from the subject line, 'Could not lock the file "/var/tmp/gconf-test-locking-file-blah"'. It says that it's an NFS locking error, but I'm not using NFS. Do you think that the packages from 7-stable are simply not compatible with 7.0-RELEASE (kde works fine), or is something else going on? My dmesg follows: Copyright (c) 1992-2008 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.0-RELEASE #0: Sat Nov 15 00:34:06 PST 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/NOEHCI Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Turion(tm) 64 X2 Mobile Technology TL-50 (1596.01-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x40f82 Stepping = 2 Features=0x178bfbff Features2=0x2001 AMD Features=0xea500800 AMD Features2=0x1f Cores per package: 2 usable memory = 924700672 (881 MB) avail memory = 890621952 (849 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) hptrr: HPT RocketRAID controller driver v1.1 (Nov 15 2008 00:33:42) acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, 1000 (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x8008-0x800b on acpi0 acpi_ec0: port 0x62,0x66 on acpi0 cpu0: on acpi0 powernow0: on cpu0 cpu1: on acpi0 powernow1: on cpu1 acpi_lid0: on acpi0 acpi_button0: on acpi0 acpi_button1: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vgapci0: port 0x9000-0x90ff mem 0xc800-0xcfff,0xc010-0xc010 irq 17 at device 5.0 on pci1 pcib2: at device 4.0 on pci0 pci2: on pcib2 pcib3: at device 5.0 on pci0 pci4: on pcib3 ohci0: mem 0xc0004000-0xc0004fff irq 19 at device 19.0 on pci0 ohci0: [GIANT-LOCKED] ohci0: [ITHREAD] usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 4 ports with 4 removable, self powered ohci1: mem 0xc0005000-0xc0005fff irq 19 at device 19.1 on pci0 ohci1: [GIANT-LOCKED] ohci1: [ITHREAD] usb1: OHCI version 1.0, legacy support usb1: on ohci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 4 ports with 4 removable, self powered pci0: at device 19.2 (no driver attached) pci0: at device 20.0 (no driver attached) atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x8410-0x841f irq 16 at device 20.1 on pci0 ata0: on atapci0 ata0: [ITHREAD] ata1: on atapci0 ata1: [ITHREAD] pcm0: mem 0xc000-0xc0003fff irq 16 at device 20.2 on pci0 pcm0: [ITHREAD] isab0: at device 20.3 on pci0 isa0: on isab0 pcib4: at device 20.4 on pci0 pci6: on pcib4 rl0: port 0xa000-0xa0ff mem 0xc021-0xc02100ff irq 21 at device 1.0 on pci6 miibus0: on rl0 rlphy0: PHY 0 on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: Ethernet address: 00:16:d4:14:c8:0f rl0: [ITHREAD] ath0: mem 0xc020-0xc020 irq 22 at device 2.0 on pci6 ath0: [ITHREAD] ath0: using obsoleted if_watchdog interface ath0: Ethernet address: 00:16:ce:7f:d8:05 ath0: mac 7.8 phy 4.5 radio 5.6 cbb0: mem 0xc0211000-0xc0211fff irq 20 at device 4.0 on pci6 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 cbb0: [ITHREAD] pci6: at device 4.1 (no driver attached) pci6: at device 4.2 (no driver attached) pci6: at device 4.3 (no driver attached) pci6: at device 4.4 (no driver attached) acpi_tz0: on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: [ITHREAD] psm0: model Synaptics Touchpad, device ID 0 battery0: on acpi0 acpi_acad0: on acpi0 orm0: at iomem 0xc-0xcefff,0xcf000-0xc on isa0 ppc0: cannot reserve I/O port range sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 8250 or not responding sio0: [FILTER] sio1: configured irq 3 not i
Re: just a test mail
Alex Zhang <[EMAIL PROTECTED]> wrote: > I want to submit a question to Mail list; I hope to get help in time. > Thanks Never, ever send test emails to freebsd-questions. From the Handbook: If you wish to test your ability to send to FreeBSD lists, send a test message to freebsd-test. Please do not send test messages to any other list. -- Sahil Tandon <[EMAIL PROTECTED]> ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
just a test mail
Hi, Dear admin I want to submit a question to Mail list; I hope to get help in time. Thanks BR Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to test an unsupported scanner (CanoScan LiDe 90)?
Hello! Polytropon schrieb: Hi! On Sun, 14 Sep 2008 11:40:54 +0200, Peter Ulrich Kruppa <[EMAIL PROTECTED]> wrote: Peter Ulrich Kruppa schrieb: I have purchased a scanner yet unsupported by sane (CanoScan LiDe 90). Mayve the SANE team will get this scanner to work later on. But at this point in time, the scanner will be outdated. :-) Perhaps they can get it running before my WinXP laptop is outdated :-) Actually I wonder if I have got a general communication problem between FreeBSD and the scanner or if the sane-backend itself is unusable. If I could make the scanner react somehow I could ask people on sane-devel list for good ideas. Greetings, Uli. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to test an unsupported scanner (CanoScan LiDe 90)?
Hi! Seems that the CanoScan LiDe 90 is one of the scanners built by Canon that are not supported well. That's a reason to avoid them. :-) I had similar issues with a LiDE 45 (I think it was), and I did soon replace it with a SCSI scanner that worked out of the box without problems. On Sun, 14 Sep 2008 11:40:54 +0200, Peter Ulrich Kruppa <[EMAIL PROTECTED]> wrote: > Peter Ulrich Kruppa schrieb: > > I have purchased a scanner yet unsupported by sane > > (CanoScan LiDe 90). Mayve the SANE team will get this scanner to work later on. But at this point in time, the scanner will be outdated. :-) > In the meantime I have played around a little bit: > I put vendor and product id's into > /usr/src/sys/dev/usb/uscanner.c and usbdevs and rebuilt > my kernel. > So now I get ># dmesg | grep uscanner >uscanner0: addr 2> on uhub1 > which changes: ># sane-find-scanner -q >found USB scanner (vendor=0x04a9, product=0x1900) at >/dev/uscanner0 > Also I tried an appropriate entry in > /usr/local/etc/sane/genesys.conf > but the result of ># scanimage -L > remains the same (not identified) and ># scanimage -d genesys:/dev/uscanner0 > image.pnm >scanimage: open of device genesys:/dev/uscanner0 failed: >Invalid argument This indicates that this scanner works differently than those usually supported by the genesys backend. I "love" Canon for making things complicated exactly this way. Maybe this scanner is compatible to another driver, but that's only a guess. Maybe it's not compatible to anything that exists. -- Polytropon >From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to test an unsupported scanner (CanoScan LiDe 90)?
Peter Ulrich Kruppa schrieb: I have purchased a scanner yet unsupported by sane (CanoScan LiDe 90). It is at least detected by # sane-find-scanner -q found USB scanner (vendor=0x04a9 [Canon], product=0x1900 [CanoScan], chip=GL842) at libusb:/dev/usb1:/dev/ugen0 - No /dev/uscanner0 is produced. - # scanimage -L says no scanners were identified. I would like to test if it might work with sane-genesys backend. How can I do this? I am running FreeBSD 7.1-PRERELEASE amd64 . In the meantime I have played around a little bit: I put vendor and product id's into /usr/src/sys/dev/usb/uscanner.c and usbdevs and rebuilt my kernel. So now I get # dmesg | grep uscanner uscanner0: on uhub1 which changes: # sane-find-scanner -q found USB scanner (vendor=0x04a9, product=0x1900) at /dev/uscanner0 Also I tried an appropriate entry in /usr/local/etc/sane/genesys.conf but the result of # scanimage -L remains the same (not identified) and # scanimage -d genesys:/dev/uscanner0 > image.pnm scanimage: open of device genesys:/dev/uscanner0 failed: Invalid argument Greetings, Uli. Thanks for your answers, comments, help, etc.. Greetings, Uli. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
How to test an unsupported scanner (CanoScan LiDe 90)?
Hello list, I have purchased a scanner yet unsupported by sane (CanoScan LiDe 90). It is at least detected by # sane-find-scanner -q found USB scanner (vendor=0x04a9 [Canon], product=0x1900 [CanoScan], chip=GL842) at libusb:/dev/usb1:/dev/ugen0 - No /dev/uscanner0 is produced. - # scanimage -L says no scanners were identified. I would like to test if it might work with sane-genesys backend. How can I do this? I am running FreeBSD 7.1-PRERELEASE amd64 . Thanks for your answers, comments, help, etc.. Greetings, Uli. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to test the uptime of a webserver?
On Thu, Sep 4, 2008 at 9:05 PM, Redd Vinylene <[EMAIL PROTECTED]>wrote: > On Thu, Sep 4, 2008 at 8:58 PM, Redd Vinylene <[EMAIL PROTECTED]>wrote: > >> >> On Sun, Aug 31, 2008 at 4:59 PM, Matthew Seaman < >> [EMAIL PROTECTED]> wrote: >> >>> Redd Vinylene wrote: >>> On Sun, Aug 31, 2008 at 2:22 AM, Moises Castellanos <[EMAIL PROTECTED]> wrote: > > On Sun, Aug 31, 2008 at 7:05 PM, Redd Vinylene <[EMAIL PROTECTED] > > > wrote: > >>> I got this dedicated server which is exposed to DDoS attacks quite >> frequently. Say I need to host a website on it, is there any way of >> telling how often it is actually online (to the rest of the world)? >> >> Maybe make some sort of ping script from a remote server? >> > >>> You can install nagios and monitor the web server. It will send you > an > email when > the server is down and when is up again. With this information you can > know > the uptime > of the web server. > >>> I'd have to install Nagios on a different server then, right? I doubt the actual server knows when its ISP's link drops (or just slows down) due to an attack. >>> >>> Not necessarily. You can install nagios on your web server and use it >>> to monitor a server at the other end of your wan link -- usually a >>> machine in your ISPs infrastructure[*] -- on the basis that if you can >>> get packets out, then other people can get packets in. The trick is to >>> monitor something that isn't too far away, or you'll end up monitoring the >>> availability of other people's networks, rather than your own. >>> >>> There's a lot more can be done than just monitoring connectivity by >>> sending ICMP ping packets every so often. There are any number of >>> ways a web server can go wrong -- processes can crash, critical disk >>> partitions can fill up, load spikes can overwhelm the machine's capacity. >>> You can develop a range of different nagios tests that should tell you >>> pretty much at a glance just what has gone wrong. Takes all the fun out >>> of diagnosing the problems perhaps, but it does mean you'll be back to >>> bed sooner when the pager goes off in the small hours. >>> >>>Cheers, >>> >>>Matthew >>> >>> [*] Some ISPs provide machines specifically for this purpose. >>> >>> -- >>> Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard >>> Flat 3 >>> PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate >>> Kent, CT11 9PW >>> >>> >> Thank you guys. I'm looking for the simplest solution though, like a >> simple oneliner, or a shell script. >> >> Anybody have an idea? >> >> -- >> http://www.home.no/reddvinylene >> > > I'll try to write a simple shell script and report back to y'all. > > -- > http://www.home.no/reddvinylene > Perfection is achieved, not when there's nothing left to add, but when there's nothing left to take away :) while sleep 555; do wget http:// -O /dev/null -t 1 || mail -s "" <<< "Host is down"; done -- http://www.home.no/reddvinylene ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to test the uptime of a webserver?
On Thu, Sep 4, 2008 at 8:58 PM, Redd Vinylene <[EMAIL PROTECTED]>wrote: > > On Sun, Aug 31, 2008 at 4:59 PM, Matthew Seaman < > [EMAIL PROTECTED]> wrote: > >> Redd Vinylene wrote: >> >>> On Sun, Aug 31, 2008 at 2:22 AM, Moises Castellanos <[EMAIL PROTECTED]> >>> wrote: >>> On Sun, Aug 31, 2008 at 7:05 PM, Redd Vinylene <[EMAIL PROTECTED]> wrote: >>> >> I got this dedicated server which is exposed to DDoS attacks quite > frequently. Say I need to host a website on it, is there any way of > telling how often it is actually online (to the rest of the world)? > > Maybe make some sort of ping script from a remote server? > >> You can install nagios and monitor the web server. It will send you an email when the server is down and when is up again. With this information you can know the uptime of the web server. >>> >> I'd have to install Nagios on a different server then, right? I doubt >>> the actual server knows when its ISP's link drops (or just slows down) >>> due to an attack. >>> >> >> Not necessarily. You can install nagios on your web server and use it >> to monitor a server at the other end of your wan link -- usually a >> machine in your ISPs infrastructure[*] -- on the basis that if you can get >> packets out, then other people can get packets in. The trick is to monitor >> something that isn't too far away, or you'll end up monitoring the >> availability of other people's networks, rather than your own. >> >> There's a lot more can be done than just monitoring connectivity by >> sending ICMP ping packets every so often. There are any number of >> ways a web server can go wrong -- processes can crash, critical disk >> partitions can fill up, load spikes can overwhelm the machine's capacity. >> You can develop a range of different nagios tests that should tell you >> pretty much at a glance just what has gone wrong. Takes all the fun out >> of diagnosing the problems perhaps, but it does mean you'll be back to >> bed sooner when the pager goes off in the small hours. >> >>Cheers, >> >>Matthew >> >> [*] Some ISPs provide machines specifically for this purpose. >> >> -- >> Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard >> Flat 3 >> PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate >> Kent, CT11 9PW >> >> > Thank you guys. I'm looking for the simplest solution though, like a simple > oneliner, or a shell script. > > Anybody have an idea? > > -- > http://www.home.no/reddvinylene > I'll try to write a simple shell script and report back to y'all. -- http://www.home.no/reddvinylene ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to test the uptime of a webserver?
On Sun, Aug 31, 2008 at 4:59 PM, Matthew Seaman < [EMAIL PROTECTED]> wrote: > Redd Vinylene wrote: > >> On Sun, Aug 31, 2008 at 2:22 AM, Moises Castellanos <[EMAIL PROTECTED]> >> wrote: >> >>> >>> On Sun, Aug 31, 2008 at 7:05 PM, Redd Vinylene <[EMAIL PROTECTED]> >>> wrote: >>> >> > I got this dedicated server which is exposed to DDoS attacks quite frequently. Say I need to host a website on it, is there any way of telling how often it is actually online (to the rest of the world)? Maybe make some sort of ping script from a remote server? >>> > You can install nagios and monitor the web server. It will send you an >>> email when >>> the server is down and when is up again. With this information you can >>> know >>> the uptime >>> of the web server. >>> >> > I'd have to install Nagios on a different server then, right? I doubt >> the actual server knows when its ISP's link drops (or just slows down) >> due to an attack. >> > > Not necessarily. You can install nagios on your web server and use it > to monitor a server at the other end of your wan link -- usually a > machine in your ISPs infrastructure[*] -- on the basis that if you can get > packets out, then other people can get packets in. The trick is to monitor > something that isn't too far away, or you'll end up monitoring the > availability of other people's networks, rather than your own. > > There's a lot more can be done than just monitoring connectivity by > sending ICMP ping packets every so often. There are any number of > ways a web server can go wrong -- processes can crash, critical disk > partitions can fill up, load spikes can overwhelm the machine's capacity. > You can develop a range of different nagios tests that should tell you > pretty much at a glance just what has gone wrong. Takes all the fun out > of diagnosing the problems perhaps, but it does mean you'll be back to > bed sooner when the pager goes off in the small hours. > >Cheers, > >Matthew > > [*] Some ISPs provide machines specifically for this purpose. > > -- > Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard > Flat 3 > PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate > Kent, CT11 9PW > > Thank you guys. I'm looking for the simplest solution though, like a simple oneliner, or a shell script. Anybody have an idea? -- http://www.home.no/reddvinylene ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to test the uptime of a webserver?
Redd Vinylene wrote: On Sun, Aug 31, 2008 at 2:22 AM, Moises Castellanos <[EMAIL PROTECTED]> wrote: On Sun, Aug 31, 2008 at 7:05 PM, Redd Vinylene <[EMAIL PROTECTED]> wrote: I got this dedicated server which is exposed to DDoS attacks quite frequently. Say I need to host a website on it, is there any way of telling how often it is actually online (to the rest of the world)? Maybe make some sort of ping script from a remote server? You can install nagios and monitor the web server. It will send you an email when the server is down and when is up again. With this information you can know the uptime of the web server. I'd have to install Nagios on a different server then, right? I doubt the actual server knows when its ISP's link drops (or just slows down) due to an attack. Not necessarily. You can install nagios on your web server and use it to monitor a server at the other end of your wan link -- usually a machine in your ISPs infrastructure[*] -- on the basis that if you can get packets out, then other people can get packets in. The trick is to monitor something that isn't too far away, or you'll end up monitoring the availability of other people's networks, rather than your own. There's a lot more can be done than just monitoring connectivity by sending ICMP ping packets every so often. There are any number of ways a web server can go wrong -- processes can crash, critical disk partitions can fill up, load spikes can overwhelm the machine's capacity. You can develop a range of different nagios tests that should tell you pretty much at a glance just what has gone wrong. Takes all the fun out of diagnosing the problems perhaps, but it does mean you'll be back to bed sooner when the pager goes off in the small hours. Cheers, Matthew [*] Some ISPs provide machines specifically for this purpose. -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: How to test the uptime of a webserver?
Redd Vinylene wrote: On Sun, Aug 31, 2008 at 2:22 AM, Moises Castellanos <[EMAIL PROTECTED]> wrote: On Sun, Aug 31, 2008 at 7:05 PM, Redd Vinylene <[EMAIL PROTECTED]> wrote: Hello hello! I got this dedicated server which is exposed to DDoS attacks quite frequently. Say I need to host a website on it, is there any way of telling how often it is actually online (to the rest of the world)? Maybe make some sort of ping script from a remote server? Hello, You can install nagios and monitor the web server. It will send you an email when the server is down and when is up again. With this information you can know the uptime of the web server. I'd have to install Nagios on a different server then, right? I doubt the actual server knows when its ISP's link drops (or just slows down) due to an attack. You can easily get nagios to test the web server sitting on the same machine its installed on and you can also get nagios to ping some external target to test the link. However if the link is down that won't help you, so basically yes it would be wise to have an external nagios server. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to test the uptime of a webserver?
Redd Vinylene wrote: On Sun, Aug 31, 2008 at 2:22 AM, Moises Castellanos <[EMAIL PROTECTED]> wrote: On Sun, Aug 31, 2008 at 7:05 PM, Redd Vinylene <[EMAIL PROTECTED]> wrote: Hello hello! I got this dedicated server which is exposed to DDoS attacks quite frequently. Say I need to host a website on it, is there any way of telling how often it is actually online (to the rest of the world)? Maybe make some sort of ping script from a remote server? Hello, You can install nagios and monitor the web server. It will send you an email when the server is down and when is up again. With this information you can know the uptime of the web server. I'd have to install Nagios on a different server then, right? I doubt the actual server knows when its ISP's link drops (or just slows down) due to an attack. You can easily get nagios to test the web server sitting on the same machine its installed on and you can also get nagios to ping some external target to test the link. However if the link is down that won't help you, so basically yes it would be wise to have an external nagios server. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to test the uptime of a webserver?
On Sun, Aug 31, 2008 at 2:22 AM, Moises Castellanos <[EMAIL PROTECTED]> wrote: > > > On Sun, Aug 31, 2008 at 7:05 PM, Redd Vinylene <[EMAIL PROTECTED]> > wrote: >> >> Hello hello! >> >> I got this dedicated server which is exposed to DDoS attacks quite >> frequently. Say I need to host a website on it, is there any way of >> telling how often it is actually online (to the rest of the world)? >> >> Maybe make some sort of ping script from a remote server? >> >> >> -- >> http://www.home.no/reddvinylene >> ___ >> freebsd-questions@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to >> "[EMAIL PROTECTED]" > > >Hello, > > You can install nagios and monitor the web server. It will send you an > email when > the server is down and when is up again. With this information you can know > the uptime > of the web server. I'd have to install Nagios on a different server then, right? I doubt the actual server knows when its ISP's link drops (or just slows down) due to an attack. -- http://www.home.no/reddvinylene ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to test the uptime of a webserver?
Redd Vinylene wrote: Hello hello! I got this dedicated server which is exposed to DDoS attacks quite frequently. Say I need to host a website on it, is there any way of telling how often it is actually online (to the rest of the world)? Maybe make some sort of ping script from a remote server? http://www.nagios.org/ Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
How to test the uptime of a webserver?
Hello hello! I got this dedicated server which is exposed to DDoS attacks quite frequently. Say I need to host a website on it, is there any way of telling how often it is actually online (to the rest of the world)? Maybe make some sort of ping script from a remote server? -- http://www.home.no/reddvinylene ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
squid hello write test failed
Dear All This is a amd64 box with FreeBSD 6.3. So far it is only acting as a firewall (with PF). Yesterday I installed squid via ports with a pretty vanilla configuration. I.e. no neighbour caches, just to be used as a standalone cache for users from the inside net. No interception caching (yet). Squid was not yet put under heavy load - in fact I am so far the only person using it. Everything worked fine yesterday. However, squid "died" after "squid -k rotate" was executed by cron over night. Here is what it came up with after (successful) log rotation: 2008/04/23 04:20:00| storeDirWriteCleanLogs: Starting... 2008/04/23 04:20:00| Finished. Wrote 1706 entries. 2008/04/23 04:20:00| Took 0.0 seconds (1714572.9 entries/sec). 2008/04/23 04:20:00| aioSync: flushing pending I/O operations 2008/04/23 04:20:00| aioSync: done 2008/04/23 04:20:00| logfileRotate: /usr/local/squid/logs/access.log 2008/04/23 04:20:00| sendto FD 12: (1) Operation not permitted 2008/04/23 04:20:00| ipcCreate: CHILD: hello write test failed Squid was running and accepting connections on port 3128, but they were not carried out any longer. I then killed squid (actually I needed kill -9 to bring it down) and made sure no more squid processes are running. But now, every time I try to start squid - manually, or via rc.d - I get the same messages as above. The "FD" number varies, but everything else stays the same. There were no other changes made on the machine in between that I am aware of. What is going on here? Regards Tobias FWIW, here is my config: cache_log /usr/local/squid/logs/cache.log cache_access_log /usr/local/squid/logs/access.log cache_store_log none connect_timeout 2 minutes log_fqdn on cache_effective_user squid http_port 3128 acl all src 0.0.0.0/0.0.0.0 acl manager proto cache_object acl localhost src 127.0.0.1/255.255.255.255 acl to_localhost dst 127.0.0.0/8 acl SSL_ports port 443 acl Safe_ports port 80 # http acl Safe_ports port 21 # ftp acl Safe_ports port 443 # https acl Safe_ports port 70 # gopher acl Safe_ports port 210 # wais acl Safe_ports port 1025-65535 # unregistered ports acl Safe_ports port 280 # http-mgmt acl Safe_ports port 488 # gss-http acl Safe_ports port 591 # filemaker acl Safe_ports port 777 # multiling http acl CONNECT method CONNECT http_access allow manager localhost http_access deny manager http_access deny !Safe_ports http_access deny CONNECT !SSL_ports http_access deny to_localhost acl inside_net src xxx.xxx.xxx.0/24 http_access allow inside_net http_access allow localhost http_access deny all cache_mgr [EMAIL PROTECTED] maximum_object_size 32 MB cache_replacement_policy heap LFUDA cache_dir aufs /usr/local/squid/cache 32768 32 256 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: This is a test, please ignore it.
"Jie Ouyang" <[EMAIL PROTECTED]> wrote: > > Test Please use the [EMAIL PROTECTED] mailing list for testing. -- Bill Moran http://www.potentialtech.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
This is a test, please ignore it.
Test ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Refurbished Wireless Test and Repair Values
We Sell Worldwide Rentals and Leasing Available Renting or leasing test equipment is todays answer. Renting test equipment allows you to acquire test equipment without the investment of ownership. Renting test equipment is an ideal solution for companies that need additional test equipment on short notice or need test equipment for short periods of time. Rent test equipment for special projects, replace failed equipment, or evaluate test equipment before purchasing and avoid long lead times. Test Equipment Connection is expanding its rental inventory and investing in the newest and most popular test equipment. Our inventory is growing and changes daily. We offer over 28,000 test instruments from over 250 manufacturers. When you rent test equipment, rental payments are treated as operating expenses and not part of your capital equipment budget. Call or Email for a Quote Today Rental Quote Request Tight Capital Budget? - No Problem! Check Out These High Quality Refurbished Equipment Specials and Maximize Your Budget. Anritsu MT8220A/40/41 Sale $8,995 Anritsu S331B Sale $3,995 Anritsu S332C Sale $6,895 Anritsu ML2437A Sale $3,995 Agilent E6380A Sale $3,500 Agilent E4436B/Options Sale $15,900 Agilent 8712ET/1EC Sale $9,800 IFR COM120B Sale $9,290 HP 4284A Sale $9,990 HP 8560EC Sale $23,000 HP 8720D with options On Sale Call R&S FSH3 On Sale Call Over 15 Years of Sales, Service and Selection Rohde & Schwarz SME03 Sale $5,490 IFR 2945A Sale 9,495 Anritsu S332C Sale $6,895 Anritsu S331C Sale $5,495 Anritsu S331A Sale $2,995 Agilent 8753ES Sale $22,000 Tektronix TVS645 Sale $2,750 Agilent 89431A Sale $6,890 Test Equipment Connection is Actively Purchasing De-installed, Excess, New-Surplus, Off-Lease and Underutilized Equipment. Click Here for a Cash Offer R&S FSH6.26/B1/Z3 Sale $19,190 JDSU SDA5000 Sale $6,990 JDSU FST2802 Sale $8,490 JDSU FST-2310 Equipped for DS1, DS3, OC-3, & OC-12 Call JDSU ANT-5 Equipped for STM-1/-4 On Sale Call Tektronix TDS3032 Sale $3,000 Tektronix TDS3034 Sale $3,895 Tektronix TDS3054B Sale $8,490 HP 8561E Sale $11,980 Marconi 2031 Sale $3,895 Agilent E4436B w/options On Sale Call HP 8720ES/10/12/400 Sale $55,000 HP 54540C Sale $2,495 HP 8648C/1E6 Sale $7,290 Our technicians are fully trained and have extensive calibration and repair expertise on the widest variety of makes & models. We provide high quality repair and calibration services at competitive prices with responsive turn around times for evaluation, repair and calibration. N.I.S.T. traceable certificates in accordance with MIL-STD 45662A and ANSI/NSCL 540-1 can be provided with all repairs. In addition, ISO 9001-2000 UL registered calibrations and ISO/IEC 17025 calibrations accredited by A2LA are available for select items. No Capital Budget? - No Problem! We Repair and Calibrate So You Can Utilize The Equipment You Already Have. Free Evaluation Coupon Below! Click Here to View This Page on the Internet Toll Free USA & Canada 800-615-8378 Direct Worldwide 407-804-1184 email [EMAIL PROTECTED] 30 Skyline Drive Lake Mary, FL 32746 This email is sent in accordance with the US CAN-SPAM Act. *Removal* requests* can be sent to this address and will be honored and respected If you want to dis-continue this mailing click on the following email address or respond with *un-subscribe* in the subject line to: [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: test
On Fri, Jan 25, 2008 at 11:52:17PM -0800, Gary Kline wrote: > test > -- > Gary Kline [EMAIL PROTECTED] www.thought.org Public Service Unix > http://jottings.thought.org http://transfinite.thought.org Well, surprise, surprise! A glance at [EMAIL PROTECTED] [ rather than [EMAIL PROTECTED] qual'd DN] proves that the following two lines do force sendmail to rewrite: aristotle.thought.org.mc:MASQUERADE_AS(`thought.org') aristotle.thought.org.mc-FEATURE(masquerade_envelope) Chuck, your pointer was right, but I didn't understand the fine points. The ``FEATURE()'' line mmust accompany the ``MASQUERADE_AS()'' LINE. And, obviously, with the proper strings within the parens. I found this on a Google listing after about 45-50 mins of searching. This is one of those fine tidbits that aren't widely known, but very useful gary PS: Hope this works -- Gary Kline Seattle BSD Users' Group (seabug) | [EMAIL PROTECTED] Thought Unlimited Org's Alternate Email Site http://www.magnesium.net/~kline To live is not a necessity; but to live honorably...is a necessity. -Kant ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: test
On 25/01/2008, Gary Kline <[EMAIL PROTECTED]> wrote: > > > Well, yesterday when I tried mailing, i could have hit keystrokes > until the cows came home and no characters were echoed. Evidently, > I did _something_ to kdemail //KMail to let this work. Possibly after I > pkg_deleted evolution. > please don't spam this list, use test@ instead :) > hm. > > > -- Forwarded Message -- > > Subject: test > Date: Thursday 24 January 2008 > From: Gary Kline <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > > testing, surprise, surprise. > -- > Gary Kline [EMAIL PROTECTED] www.thought.org Public Service Unix > http://jottings.thought.org http://transfinite.thought.org > > --- > > -- > Gary Kline [EMAIL PROTECTED] www.thought.org Public Service Unix > http://jottings.thought.org http://transfinite.thought.org > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > -- Regards, Kimi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Fwd: test
Well, yesterday when I tried mailing, i could have hit keystrokes until the cows came home and no characters were echoed. Evidently, I did _something_ to kdemail //KMail to let this work. Possibly after I pkg_deleted evolution. hm. -- Forwarded Message -- Subject: test Date: Thursday 24 January 2008 From: Gary Kline <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] testing, surprise, surprise. -- Gary Kline [EMAIL PROTECTED] www.thought.org Public Service Unix http://jottings.thought.org http://transfinite.thought.org --- -- Gary Kline [EMAIL PROTECTED] www.thought.org Public Service Unix http://jottings.thought.org http://transfinite.thought.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Test
On Tue, 18 Sep 2007, EaRSHoT wrote: tets Read The Friendly Handbook, http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/eresources.html#ERESOURCES-MAIL Note: If you wish to test your ability to send to FreeBSD lists, send a test message to freebsd-test. Please do not send test messages to any other list. Make special note of that last sentence. -- Chris Hill [EMAIL PROTECTED] ** [ Busy Expunging <|> ] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Test
tets ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Test on FreeBSD site
Bill Moran wrote: In response to NetOpsCenter <[EMAIL PROTECTED]>: Aloha, How long does it take for a test to be accepted or rejected on the FreeBSD test mail box? Is three minutes normal for a test to pop up? I had some FreeBSD 7 config issues and this nearly caused me to think I hadn't cleared the problem because it took quite a while to pop up. It depends on how busy the server is at the time you send it, among other factors. I haven't noticed if the mail servers are doing greylisting, but it wouldn't surprise me if they were. In this day and age, with the spam scourge and all the alleged "solutions" that everyone's mail servers use, anything less than 10 minutes for a delivery should be considered successful. Thanks for the reply. FreeBSD 7 is excellent. Applause to the Developers. I have been using FreeBSD since 2. something. Is there a good how to set up spam assassin for FreeBSD? Most I have tried have no FreeBSD specific file placements listsed and I can't get it to work. ~Al Plant - Honolulu, Hawaii - Phone: 808-284-2740 + http://hawaiidakine.com + http://freebsdinfo.org + [EMAIL PROTECTED] + + http://internetohana.org - Supporting - FreeBSD 6.* - 7.* + "All that's really worth doing is what we do for others."- Lewis Carrol ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Test on FreeBSD site
>> I haven't noticed if the mail servers are doing greylisting, but it >> wouldn't surprise me if they were. > > They do. That's quite the response. Care to elaborate for purposes of archive accuracy? Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Test on FreeBSD site
On 2007-08-24 06:36, Bill Moran <[EMAIL PROTECTED]> wrote: > In response to NetOpsCenter <[EMAIL PROTECTED]>: > > How long does it take for a test to be accepted or rejected on the > > FreeBSD test mail box? Is three minutes normal for a test to pop > > up? I had some FreeBSD 7 config issues and this nearly caused me to > > think I hadn't cleared the problem because it took quite a while to > > pop up. > > It depends on how busy the server is at the time you send it, among > other factors. I haven't noticed if the mail servers are doing > greylisting, but it wouldn't surprise me if they were. They are. It may take a few minutes before a message gets through, but that depends on how often the *sending* server retries. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Test on FreeBSD site
Bill Moran wrote: I haven't noticed if the mail servers are doing greylisting, but it wouldn't surprise me if they were. They do. --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Test on FreeBSD site
In response to NetOpsCenter <[EMAIL PROTECTED]>: > Aloha, > > How long does it take for a test to be accepted or rejected on the > FreeBSD test mail box? > Is three minutes normal for a test to pop up? > I had some FreeBSD 7 config issues and this nearly caused me to think I > hadn't cleared the problem because it took quite a while to pop up. It depends on how busy the server is at the time you send it, among other factors. I haven't noticed if the mail servers are doing greylisting, but it wouldn't surprise me if they were. In this day and age, with the spam scourge and all the alleged "solutions" that everyone's mail servers use, anything less than 10 minutes for a delivery should be considered successful. -- Bill Moran http://www.potentialtech.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Test on FreeBSD site
Aloha, How long does it take for a test to be accepted or rejected on the FreeBSD test mail box? Is three minutes normal for a test to pop up? I had some FreeBSD 7 config issues and this nearly caused me to think I hadn't cleared the problem because it took quite a while to pop up. Mahalo ~Al Plant - Honolulu, Hawaii - Phone: 808-284-2740 + http://hawaiidakine.com + http://freebsdinfo.org + [EMAIL PROTECTED] + + http://internetohana.org - Supporting - FreeBSD 6.* - 7.* + "All that's really worth doing is what we do for others."- Lewis Carrol ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Sending test messages (was Re: don't read it)
On 09/08/07, Jerry McAllister <[EMAIL PROTECTED]> wrote: > On Thu, Aug 09, 2007 at 10:59:44AM -0400, Bill Moran wrote: > > > In response to Jean-Pierre Trophardy <[EMAIL PROTECTED]>: > > > > > Duane Hill <[EMAIL PROTECTED]> wrote: > > > > > > > > [EMAIL PROTECTED] works fine for sending test messages. Subscribe > > > > to it and use it for test message sending. > > > > > > > > > > As you guest it was just for test message sending to THIS ONE. > > > > > > Sorry for the inconvenience. > > > > The reason for the complaint (and the reason the freebsd-test list exists) > > is that you just "inconvenienced" thousands of people who subscribe to > > this list. > > The thing I find interesting is that when someone sends one of those > so-called test messages, we get . . . . . . hopefully some balance, the 19 berative posts perhaps preventing a bouillon others. -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Sending test messages (was Re: don't read it)
On Thu, Aug 09, 2007 at 10:59:44AM -0400, Bill Moran wrote: > In response to Jean-Pierre Trophardy <[EMAIL PROTECTED]>: > > > Duane Hill <[EMAIL PROTECTED]> wrote: > > > > > > [EMAIL PROTECTED] works fine for sending test messages. Subscribe > > > to it and use it for test message sending. > > > > > > > As you guest it was just for test message sending to THIS ONE. > > > > Sorry for the inconvenience. > > The reason for the complaint (and the reason the freebsd-test list exists) > is that you just "inconvenienced" thousands of people who subscribe to > this list. The thing I find interesting is that when someone sends one of those so-called test messages, we get 19 people posting messages telling them how much they are inconveniencing so many people with the test message and rarely a single message telling the other posters how much their complaints about the test messages unconvenience people. > > As usual, this resulted in a discussion that is further inconveniencing > people ... ^^ Single exception... jerry > > The point behind that freebsd-test list is that it is configured in exactly > the same manner as other FreeBSD mailing lists. If you can subscribe and > post to freebsd-test, then you will be able to use the exact same procedure > to subscribe and post to any other FreeBSD mailing list. So there is no > reason to ever send test messages to anything other than freebsd-test. > > I'm not saying this to berate you, Jean-Pierre. My purpose is to clarify > this for anyone who may be reading, or may in the future read the mail > archives for this list. Understanding the system allows people to use it > effectively. > > -- > Bill Moran > http://www.potentialtech.com > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Sending test messages (was Re: don't read it)
In response to Jean-Pierre Trophardy <[EMAIL PROTECTED]>: > Duane Hill <[EMAIL PROTECTED]> wrote: > > > > [EMAIL PROTECTED] works fine for sending test messages. Subscribe > > to it and use it for test message sending. > > > > As you guest it was just for test message sending to THIS ONE. > > Sorry for the inconvenience. The reason for the complaint (and the reason the freebsd-test list exists) is that you just "inconvenienced" thousands of people who subscribe to this list. As usual, this resulted in a discussion that is further inconveniencing people ... The point behind that freebsd-test list is that it is configured in exactly the same manner as other FreeBSD mailing lists. If you can subscribe and post to freebsd-test, then you will be able to use the exact same procedure to subscribe and post to any other FreeBSD mailing list. So there is no reason to ever send test messages to anything other than freebsd-test. I'm not saying this to berate you, Jean-Pierre. My purpose is to clarify this for anyone who may be reading, or may in the future read the mail archives for this list. Understanding the system allows people to use it effectively. -- Bill Moran http://www.potentialtech.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
don't read it, test
test -- Jean-Pierre Trophardy ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: hi this is test message
Please use [EMAIL PROTECTED] for testing purposes. That's the reason it exists, and it avoids spamming 1000s of subscribers. -- Bill Moran http://www.potentialtech.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
hi this is test message
hi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
hi this is test message
___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Test Mail
___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: flash ( With details and user test results)
Norberto Meijome writes: > So I decided to give this a try again, with some mixed results. I > double checked what I was doing with the steps shown in the URL > Gaye kindly provided, it all checked out as expected. Ditto. > Downs: Flash videos, such as those in video.google, youtube and > others, load (static image is shown, start streaming), play for > about 1 second with video + sound, and then they just dissapear > from the browser, with errors from the NSPluginWrapper. I'm getting the same behavior under: FreeBSD 7.0-CURRENT #0: Thu Jun 7 08:59:28 EDT 2007 i386 I haven't tried the "running from an xtern" step, but would expect to get the same results. Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: flash ( With details and user test results)
On Mon, 2 Jul 2007 16:41:09 +1000
Norberto Meijome <[EMAIL PROTECTED]> wrote:
> ###
> ### tried with youtube.com.
> ### Flash loaded ok, simple flash stuff like the 'videos being watched now'
> worked fine.
> ### Clicking on the suggested videon on the top RHS started playing the video
> + sound, after 1 second, again:
What happened with flash9 after 1 second is that *all* flash objects in the
page simply blanked out - the one with the video, and the one with the 'videos
being watched now' which is a simple cute flash thingy with no video.
> ### this happens with CPU spiking to 100%
> ###
_
{Beto|Norberto|Numard} Meijome
"Peace can only be achieved by understanding."
Albert Einstein
I speak for myself, not my employer. Contents may be hot. Slippery when wet.
Reading disclaimers makes you go blind. Writing them is worse. You have been
Warned.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: flash ( With details and user test results)
base are no longer supported. (Gecko:42617): libgnomevfs-WARNING **: Deprecated function. User modifications to the MIME database are no longer supported. (Gecko:42617): libgnomevfs-WARNING **: Deprecated function. User modifications to the MIME database are no longer supported. (Gecko:42617): libgnomevfs-WARNING **: Deprecated function. User modifications to the MIME database are no longer supported. (Gecko:42617): libgnomevfs-WARNING **: Deprecated function. User modifications to the MIME database are no longer supported. ### ### Loaded a local .swf . It worked ok...then issued this msg. ### *** NSPlugin Wrapper *** ERROR: NPP_Destroy() invoke: Connection closed *** NSPlugin Wrapper *** ERROR: NP_Shutdown() invoke: Connection closed ### ### Reloaded the .swf, no problems this time. ### ### ### Went to video.google.com - clicked on one of the videos, randomly http://video.google.com.au/videoplay?docid=-708218345413567790 ### Video started loading, buzzing sound ( as if there was static in sound card), then video completelly blanked out ,as if it was removed from the page. Msgs showed: ### (npviewer.bin:42668): Gtk-CRITICAL **: gtk_window_resize: assertion `width > 0' failed *** NSPlugin Wrapper *** ERROR: NPP_Write() invoke: Connection closed *** NSPlugin Wrapper *** ERROR: NPP_DestroyStream() invoke: Connection closed *** NSPlugin Wrapper *** ERROR: NPP_URLNotify() invoke: Connection closed *** NSPlugin Wrapper *** ERROR: NPP_Destroy() invoke: Connection closed *** NSPlugin Wrapper *** ERROR: NPClass::Invalidate() invoke: Connection closed *** NSPlugin Wrapper *** ERROR: NP_Shutdown() invoke: Connection closed ### ### repeated test with video.google.com ### (npviewer.bin:42682): Gtk-CRITICAL **: gtk_window_resize: assertion `width > 0' failed *** NSPlugin Wrapper *** ERROR: NPP_WriteReady() invoke: Connection closed *** NSPlugin Wrapper *** ERROR: NPP_WriteReady() invoke: Connection closed [MORE AND MORE OF THE SAME, CONTINUOSLY] *** NSPlugin Wrapper *** ERROR: NPP_WriteReady() invoke: Connection closed *** NSPlugin Wrapper *** ERROR: NPP_WriteReady() invoke: Connection closed *** NSPlugin Wrapper *** ERROR: NPP_WriteReady() invoke: Connection closed ### yes, the messages were non-stop while the video.google page was open - i hit back and got : *** NSPlugin Wrapper *** ERROR: NPP_DestroyStream() invoke: Connection closed *** NSPlugin Wrapper *** ERROR: NPP_URLNotify() invoke: Connection closed *** NSPlugin Wrapper *** ERROR: NPP_Destroy() invoke: Connection closed *** NSPlugin Wrapper *** ERROR: NP_Shutdown() invoke: Connection closed ### ### tried with youtube.com. ### Flash loaded ok, simple flash stuff like the 'videos being watched now' worked fine. ### Clicking on the suggested videon on the top RHS started playing the video + sound, after 1 second, again: ### this happens with CPU spiking to 100% ### *** NSPlugin Wrapper *** ERROR: NPP_WriteReady() invoke: Connection closed *** NSPlugin Wrapper *** ERROR: NPP_NewStream() invoke: Connection closed *** NSPlugin Wrapper *** ERROR: NPP_URLNotify() invoke: Connection closed *** NSPlugin Wrapper *** ERROR: NPP_WriteReady() invoke: Connection closed *** NSPlugin Wrapper *** ERROR: NPP_WriteReady() invoke: Connection closed *** NSPlugin Wrapper *** ERROR: NPP_WriteReady() invoke: Connection closed [MORE AND MORE OF THE SAME, CONTINUOSLY] *** NSPlugin Wrapper *** ERROR: NPP_WriteReady() invoke: Connection closed *** NSPlugin Wrapper *** ERROR: NPP_WriteReady() invoke: Connection closed *** NSPlugin Wrapper *** ERROR: NPP_WriteReady() invoke: Connection closed ### ### Hit back button, bang, NPP_Destroy ### *** NSPlugin Wrapper *** ERROR: NPP_Destroy() invoke: Connection closed *** NSPlugin Wrapper *** ERROR: NPClass::Invalidate() invoke: Connection closed *** NSPlugin Wrapper *** ERROR: NPP_DestroyStream() invoke: Connection closed *** NSPlugin Wrapper *** ERROR: NPP_URLNotify() invoke: Connection closed *** NSPlugin Wrapper *** ERROR: NPP_Destroy() invoke: Connection closed *** NSPlugin Wrapper *** ERROR: NPClass::Invalidate() invoke: Connection closed *** NSPlugin Wrapper *** ERROR: NP_Shutdown() invoke: Connection closed ### ### Browsing around... non-video Flash objects. working fine ### ** NSPlugin Wrapper *** ERROR: NPP_Write() wait for reply: Connection closed *** NSPlugin Wrapper *** ERROR: NPP_DestroyStream() invoke: Connection closed *** NSPlugin Wrapper *** ERROR: NPP_GetValue() invoke: Connection closed *** NSPlugin Wrapper *** WARNING: unhandled variable 11 in NPP_GetValue() *** NSPlugin Wrapper *** ERROR: NPP_GetValue() invoke: Connection closed *** NSPlugin Wrapper *** WARNING: unhandled variable 11 in NPP_GetValue() *** NSPlugin Wrapper *** ERROR: NPP_New() invoke: Connection closed *** NSPlugin Wrapper *** ERROR: NPP_GetValue() invoke: Connection closed *** NSPlugin Wrapper *** WARNING: unhandled variable 11 in NPP_GetValue() *** NSPlugin Wrapper *** ERROR: NPP_Destroy() invoke: Connecti
Re: test
On Apr 16, 2007, at 8:52 AM, Bob Middaugh wrote: Please don't top post. Maybe he can't read and that's why the unsub link is useless? That would also explain the top posting to a degree. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: test
Please don't top post. Bob -- Original message -- From: Hangmn <[EMAIL PROTECTED]> > You group of elitist fucks...the unsub link is FUCKING USELESS > > On 4/14/07, Bill Moran <[EMAIL PROTECTED]> wrote: > > > > In response to Hangmn <[EMAIL PROTECTED]>: > > > > > GET ME OFF THIS FUCKING LIST > > > > That's a powerfully effective method of getting things done. > > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: test
On Saturday 14 April 2007, Hangmn said: > You group of elitist fucks...the unsub link is FUCKING USELESS > > On 4/14/07, Bill Moran <[EMAIL PROTECTED]> wrote: > > In response to Hangmn <[EMAIL PROTECTED]>: > > > GET ME OFF THIS FUCKING LIST > > > > That's a powerfully effective method of getting things done. > > > > First off, the use of the word FUCKING is a well-known method to > > convince people to come to your aid. I believe it was Napoleon > > who stated, "By inserting 'FUCKING' in front of every FUCKING > > noun in every FUCKING sentence, I have managed to motivate my > > FUCKING soldiers more so than any other FUCKING method I have > > tried." > > > > Secondly, the use of all caps is known to be an efficient method > > of getting > > your point across. Internet experts agree that mailing lists are > > very loud, and the only way you're guaranteed to be heard is to > > SHOUT all the time. I'm glad you've caught on to this fine point > > of netiquette. > > > > Thirdly, replying to an arbitrary message instead of taking the > > time to contact the right people is a fabulously effective method > > of getting things > > done. Obviously, the guy who sent this test message, as well as > > others who read it are most likely to be the people who can > > actually _do_ anything > > about your problem. > > > > And lastly, leaving out all the details of your problem is > > guaranteed to expedite the fix of your problem. Obviously those > > details, such as a copy of an offending message with fully > > headers, or a list of the steps you've tried to take in > > resolution of the problem, would only confused the technically > > adept people who could actually research and fix your problem. > > Leaving them out is good practice. > > > > > On 4/11/07, Bill Moran <[EMAIL PROTECTED]> wrote: > > > > Please use the [EMAIL PROTECTED] mailing list for testing. It > > > > avoids spamming 1000s of inboxes with test messages. This poster with advanced intelligence also found that none of gmail's spam tools had any effect on his problem. AOL would probably be his best choice. Beech -- --- Beech Rintoul - Port Maintainer - [EMAIL PROTECTED] /"\ ASCII Ribbon Campaign | FreeBSD Since 4.x \ / - NO HTML/RTF in e-mail | http://www.freebsd.org X - NO Word docs in e-mail | Latest Release: / \ - http://www.freebsd.org/releases/6.2R/announce.html --- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: test
On Sat, Apr 14, 2007 at 08:22:53AM -0400, Gerard Seibert wrote:
> On Sat, 14 Apr 2007 16:28:29 +1200
> "Juha Saarinen" <[EMAIL PROTECTED]> wrote:
>
> > On 4/14/07, Hangmn <[EMAIL PROTECTED]> wrote:
> > > GET ME OFF THIS FUCKING LIST
> >
> > No, no, this is the FreeBSD Questions list. The Fucking List is down
> > the hall, third door to your right. Just ignore the funny noises
> > there.
> >
> > If you don't want to receive mail from the FreeBSD list in question,
> > try this which is found at the end of every message to it:
> >
> > To unsubscribe, send any mail to
> > [EMAIL PROTECTED]
>
> Has anyone but me noticed that the morons who request to be removed
> from a list are inevitably 'TOP POSTERS'. They never read to the end of
> a post and therefore are not likely to see the easy to follow
> directions plainly stated there for their perusal.
I've noticed that a lot of unpleasant or inconvenient behavior tends to
go along with top posting, and TOFU in particular. I've also noticed
that this is not universal -- it's just a trend. There are a few people
whose only offense is top posting. They seem to be the exception,
however, rather than the rule.
>
> I used to be an agnostic, but now I'm not so sure.
I used to think I was indecisive, but now I'm reconsidering that
position. I plan to stop procrastinating on making a decision about
that tomorrow.
--
CCD CopyWrite Chad Perrin [ http://ccd.apotheon.org ]
print substr("Just another Perl hacker", 0, -2);
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: test
On Sat, Apr 14, 2007 at 01:18:46PM -0400, Hangmn wrote: > You group of elitist fucks...the unsub link is FUCKING USELESS > Sounds like you are the elitist jerk. A couple of days ago I wrote a long explanation about how a person could have trouble getting off a list and also how some useless idiot could manipulate the system to abusively get people stuck on the list. I suggest you go find that posting and then if you really want off the list and aren't just hanging here to exploit the opportunity to run your foul mouth and trash people who are trying to get work done, then you will try to work with the list administrators and help them help you get this taken care of. Abusive language will not help. It just makes more of us ignore you. jerry > On 4/14/07, Bill Moran <[EMAIL PROTECTED]> wrote: > > > >In response to Hangmn <[EMAIL PROTECTED]>: > > > >> GET ME OFF THIS FUCKING LIST > > > >That's a powerfully effective method of getting things done. > > > >First off, the use of the word FUCKING is a well-known method to convince > >people to come to your aid. I believe it was Napoleon who stated, "By > >inserting 'FUCKING' in front of every FUCKING noun in every FUCKING > >sentence, I have managed to motivate my FUCKING soldiers more so than > >any other FUCKING method I have tried." > > > >Secondly, the use of all caps is known to be an efficient method of > >getting > >your point across. Internet experts agree that mailing lists are very > >loud, and the only way you're guaranteed to be heard is to SHOUT all > >the time. I'm glad you've caught on to this fine point of netiquette. > > > >Thirdly, replying to an arbitrary message instead of taking the time to > >contact the right people is a fabulously effective method of getting > >things > >done. Obviously, the guy who sent this test message, as well as others > >who read it are most likely to be the people who can actually _do_ > >anything > >about your problem. > > > >And lastly, leaving out all the details of your problem is guaranteed to > >expedite the fix of your problem. Obviously those details, such as a > >copy of an offending message with fully headers, or a list of the steps > >you've tried to take in resolution of the problem, would only confused > >the technically adept people who could actually research and fix your > >problem. Leaving them out is good practice. > > > >> > >> On 4/11/07, Bill Moran <[EMAIL PROTECTED]> wrote: > >> > > >> > > >> > Please use the [EMAIL PROTECTED] mailing list for testing. It avoids > >> > spamming 1000s of inboxes with test messages. > >> > > >> > In response to Bill Hall <[EMAIL PROTECTED]>: > >> > > >> > > > >> > > -- > >> > > Bill Hall > >> > > Manager, Occupant Protection Program > >> > > UNC Highway Safety Research Center > >> > > 730 Martin Luther King Jr. Blvd., Suite 300 > >> > > CB# 3430 > >> > > Chapel Hill, NC 27599 > >> > > > >> > > 919-962-8721 (Voice) > >> > > 800-672-4527 (toll-free in NC) > >> > > 919-962-8710 (fax) > >> > > [EMAIL PROTECTED] > >> > > http://www.hsrc.unc.edu > >> > > http://www.buckleupnc.org > >> > > > >> > > > >> > > ___ > >> > > [EMAIL PROTECTED] mailing list > >> > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > >> > > To unsubscribe, send any mail to " > >> > [EMAIL PROTECTED]" > >> > > >> > > >> > -- > >> > Bill Moran > >> > http://www.potentialtech.com > >> > ___ > >> > [EMAIL PROTECTED] mailing list > >> > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > >> > To unsubscribe, send any mail to " > >> > [EMAIL PROTECTED]" > >> > > >> > > >> ___ > >> [EMAIL PROTECTED] mailing list > >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions > >> To unsubscribe, send any mail to " > >[EMAIL PROTECTED]" > > > > > >-- > >Bill Moran > >http://www.potentialtech.com > > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: test
You group of elitist fucks...the unsub link is FUCKING USELESS On 4/14/07, Bill Moran <[EMAIL PROTECTED]> wrote: In response to Hangmn <[EMAIL PROTECTED]>: > GET ME OFF THIS FUCKING LIST That's a powerfully effective method of getting things done. First off, the use of the word FUCKING is a well-known method to convince people to come to your aid. I believe it was Napoleon who stated, "By inserting 'FUCKING' in front of every FUCKING noun in every FUCKING sentence, I have managed to motivate my FUCKING soldiers more so than any other FUCKING method I have tried." Secondly, the use of all caps is known to be an efficient method of getting your point across. Internet experts agree that mailing lists are very loud, and the only way you're guaranteed to be heard is to SHOUT all the time. I'm glad you've caught on to this fine point of netiquette. Thirdly, replying to an arbitrary message instead of taking the time to contact the right people is a fabulously effective method of getting things done. Obviously, the guy who sent this test message, as well as others who read it are most likely to be the people who can actually _do_ anything about your problem. And lastly, leaving out all the details of your problem is guaranteed to expedite the fix of your problem. Obviously those details, such as a copy of an offending message with fully headers, or a list of the steps you've tried to take in resolution of the problem, would only confused the technically adept people who could actually research and fix your problem. Leaving them out is good practice. > > On 4/11/07, Bill Moran <[EMAIL PROTECTED]> wrote: > > > > > > Please use the [EMAIL PROTECTED] mailing list for testing. It avoids > > spamming 1000s of inboxes with test messages. > > > > In response to Bill Hall <[EMAIL PROTECTED]>: > > > > > > > > -- > > > Bill Hall > > > Manager, Occupant Protection Program > > > UNC Highway Safety Research Center > > > 730 Martin Luther King Jr. Blvd., Suite 300 > > > CB# 3430 > > > Chapel Hill, NC 27599 > > > > > > 919-962-8721 (Voice) > > > 800-672-4527 (toll-free in NC) > > > 919-962-8710 (fax) > > > [EMAIL PROTECTED] > > > http://www.hsrc.unc.edu > > > http://www.buckleupnc.org > > > > > > > > > ___ > > > [EMAIL PROTECTED] mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > > To unsubscribe, send any mail to " > > [EMAIL PROTECTED]" > > > > > > -- > > Bill Moran > > http://www.potentialtech.com > > ___ > > [EMAIL PROTECTED] mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to " > > [EMAIL PROTECTED]" > > > > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to " [EMAIL PROTECTED]" -- Bill Moran http://www.potentialtech.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: test
On Sat, 14 Apr 2007 16:28:29 +1200 "Juha Saarinen" <[EMAIL PROTECTED]> wrote: > On 4/14/07, Hangmn <[EMAIL PROTECTED]> wrote: > > GET ME OFF THIS FUCKING LIST > > No, no, this is the FreeBSD Questions list. The Fucking List is down > the hall, third door to your right. Just ignore the funny noises > there. > > If you don't want to receive mail from the FreeBSD list in question, > try this which is found at the end of every message to it: > > To unsubscribe, send any mail to > [EMAIL PROTECTED] Has anyone but me noticed that the morons who request to be removed from a list are inevitably 'TOP POSTERS'. They never read to the end of a post and therefore are not likely to see the easy to follow directions plainly stated there for their perusal. -- Gerard I used to be an agnostic, but now I'm not so sure. signature.asc Description: PGP signature
Re: test
In response to Hangmn <[EMAIL PROTECTED]>: > GET ME OFF THIS FUCKING LIST That's a powerfully effective method of getting things done. First off, the use of the word FUCKING is a well-known method to convince people to come to your aid. I believe it was Napoleon who stated, "By inserting 'FUCKING' in front of every FUCKING noun in every FUCKING sentence, I have managed to motivate my FUCKING soldiers more so than any other FUCKING method I have tried." Secondly, the use of all caps is known to be an efficient method of getting your point across. Internet experts agree that mailing lists are very loud, and the only way you're guaranteed to be heard is to SHOUT all the time. I'm glad you've caught on to this fine point of netiquette. Thirdly, replying to an arbitrary message instead of taking the time to contact the right people is a fabulously effective method of getting things done. Obviously, the guy who sent this test message, as well as others who read it are most likely to be the people who can actually _do_ anything about your problem. And lastly, leaving out all the details of your problem is guaranteed to expedite the fix of your problem. Obviously those details, such as a copy of an offending message with fully headers, or a list of the steps you've tried to take in resolution of the problem, would only confused the technically adept people who could actually research and fix your problem. Leaving them out is good practice. > > On 4/11/07, Bill Moran <[EMAIL PROTECTED]> wrote: > > > > > > Please use the [EMAIL PROTECTED] mailing list for testing. It avoids > > spamming 1000s of inboxes with test messages. > > > > In response to Bill Hall <[EMAIL PROTECTED]>: > > > > > > > > -- > > > Bill Hall > > > Manager, Occupant Protection Program > > > UNC Highway Safety Research Center > > > 730 Martin Luther King Jr. Blvd., Suite 300 > > > CB# 3430 > > > Chapel Hill, NC 27599 > > > > > > 919-962-8721 (Voice) > > > 800-672-4527 (toll-free in NC) > > > 919-962-8710 (fax) > > > [EMAIL PROTECTED] > > > http://www.hsrc.unc.edu > > > http://www.buckleupnc.org > > > > > > > > > ___ > > > [EMAIL PROTECTED] mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > > To unsubscribe, send any mail to " > > [EMAIL PROTECTED]" > > > > > > -- > > Bill Moran > > http://www.potentialtech.com > > ___ > > [EMAIL PROTECTED] mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to " > > [EMAIL PROTECTED]" > > > > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- Bill Moran http://www.potentialtech.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: test
On 4/14/07, Hangmn <[EMAIL PROTECTED]> wrote: GET ME OFF THIS FUCKING LIST No, no, this is the FreeBSD Questions list. The Fucking List is down the hall, third door to your right. Just ignore the funny noises there. If you don't want to receive mail from the FreeBSD list in question, try this which is found at the end of every message to it: To unsubscribe, send any mail to [EMAIL PROTECTED] -- Juha http://www.geekzone.co.nz/juha ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: test
Chris wrote: Hangmn wrote: GET ME OFF THIS FUCKING LIST On 4/11/07, Bill Moran <[EMAIL PROTECTED]> wrote: Please use the [EMAIL PROTECTED] mailing list for testing. It avoids spamming 1000s of inboxes with test messages. In response to Bill Hall <[EMAIL PROTECTED]>: -- Bill Hall Manager, Occupant Protection Program UNC Highway Safety Research Center 730 Martin Luther King Jr. Blvd., Suite 300 CB# 3430 Chapel Hill, NC 27599 919-962-8721 (Voice) 800-672-4527 (toll-free in NC) 919-962-8710 (fax) [EMAIL PROTECTED] http://www.hsrc.unc.edu http://www.buckleupnc.org tsk, tsk, tsk - at least I was somewhat more civilized then others with my test. *evil grin* Yowch.. someone woke up on the wrong side of the bed today. Please do like the footer says and: To unsubscribe, send any mail to "[EMAIL PROTECTED]" Cheers, and best of luck, -Garrett ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: test
Hangmn wrote: > GET ME OFF THIS FUCKING LIST > > On 4/11/07, Bill Moran <[EMAIL PROTECTED]> wrote: >> >> >> Please use the [EMAIL PROTECTED] mailing list for testing. It avoids >> spamming 1000s of inboxes with test messages. >> >> In response to Bill Hall <[EMAIL PROTECTED]>: >> >> > >> > -- >> > Bill Hall >> > Manager, Occupant Protection Program >> > UNC Highway Safety Research Center >> > 730 Martin Luther King Jr. Blvd., Suite 300 >> > CB# 3430 >> > Chapel Hill, NC 27599 >> > >> > 919-962-8721 (Voice) >> > 800-672-4527 (toll-free in NC) >> > 919-962-8710 (fax) >> > [EMAIL PROTECTED] >> > http://www.hsrc.unc.edu >> > http://www.buckleupnc.org >> > >> > >> > ___ >> > [EMAIL PROTECTED] mailing list >> > http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> > To unsubscribe, send any mail to " >> [EMAIL PROTECTED]" >> >> >> -- >> Bill Moran >> http://www.potentialtech.com >> ___ >> [EMAIL PROTECTED] mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to " >> [EMAIL PROTECTED]" >> >> > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" > > tsk, tsk, tsk - at least I was somewhat more civilized then others with my test. *evil grin* -- Best regards, Chris Allow 6 to 8 weeks for delivery. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: test
GET ME OFF THIS FUCKING LIST On 4/11/07, Bill Moran <[EMAIL PROTECTED]> wrote: Please use the [EMAIL PROTECTED] mailing list for testing. It avoids spamming 1000s of inboxes with test messages. In response to Bill Hall <[EMAIL PROTECTED]>: > > -- > Bill Hall > Manager, Occupant Protection Program > UNC Highway Safety Research Center > 730 Martin Luther King Jr. Blvd., Suite 300 > CB# 3430 > Chapel Hill, NC 27599 > > 919-962-8721 (Voice) > 800-672-4527 (toll-free in NC) > 919-962-8710 (fax) > [EMAIL PROTECTED] > http://www.hsrc.unc.edu > http://www.buckleupnc.org > > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to " [EMAIL PROTECTED]" -- Bill Moran http://www.potentialtech.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to " [EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: test
Please use the [EMAIL PROTECTED] mailing list for testing. It avoids spamming 1000s of inboxes with test messages. In response to Bill Hall <[EMAIL PROTECTED]>: > > -- > Bill Hall > Manager, Occupant Protection Program > UNC Highway Safety Research Center > 730 Martin Luther King Jr. Blvd., Suite 300 > CB# 3430 > Chapel Hill, NC 27599 > > 919-962-8721 (Voice) > 800-672-4527 (toll-free in NC) > 919-962-8710 (fax) > [EMAIL PROTECTED] > http://www.hsrc.unc.edu > http://www.buckleupnc.org > > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- Bill Moran http://www.potentialtech.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
test
-- Bill Hall Manager, Occupant Protection Program UNC Highway Safety Research Center 730 Martin Luther King Jr. Blvd., Suite 300 CB# 3430 Chapel Hill, NC 27599 919-962-8721 (Voice) 800-672-4527 (toll-free in NC) 919-962-8710 (fax) [EMAIL PROTECTED] http://www.hsrc.unc.edu http://www.buckleupnc.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
test
-- Bill Hall Manager, Occupant Protection Program UNC Highway Safety Research Center 730 Martin Luther King Jr. Blvd., Suite 300 CB# 3430 Chapel Hill, NC 27599 919-962-8721 (Voice) 800-672-4527 (toll-free in NC) 919-962-8710 (fax) [EMAIL PROTECTED] http://www.hsrc.unc.edu http://www.buckleupnc.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Test
Yanno - I was just gonna let this go but it seems a simple "sorry" isn't good enough for some that simply don't feel as if life is complete without some sorta bitchin' Grow up, get a life, move on. It wont be the first time someone does this - and it certainly won't be the last - much less have the offender (me in this case) apologize for it... Apology ... rescinded As if we had wronged you - "YANNO, I was gonna let this one go, but you screwed up!!!" You have some serious boundary issues, Silva. Until you change your behavior, don't be surprised if your "Apology... rescinded" becomes "Subscriber... booted". SC ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
The dynamics of a mailing list (was Re: Test)
In response to Chris <[EMAIL PROTECTED]>: > Simon Chang wrote: > > Hear, hear. > > > > Chris, please remember NOT to do this again. > > > > SC > > Yanno - I was just gonna let this go but it seems a simple "sorry" isn't > good enough for some that simply don't feel as if life is complete > without some sorta bitchin' > > Grow up, get a life, move on. It wont be the first time someone does > this - and it certainly won't be the last - much less have the offender > (me in this case) apologize for it... For crying out loud. There are x000 people on this mailing list. When you do something that's considered unacceptable you'll immediately have two scenarios: 1) Some people just _have_ to speak their peace, even if it's already been spoken by someone else. 2) Many people will (literally) post their objection simultaneously, and you'll then feel like the whole world is jumping on you because you get 5 or 6 messages at once. However, responding like you did, Chris, only makes it worse. Keep in mind that it's less than 1% of the list members that are making a fuss right now. Too often, this list traffic ends up clogged with some sort of flame war that _only_ 5 or 6 people are actually participating in. Remember, again, that's less than 1% of the total list participants. Yes, the test@ list exists to keep test messages off the other lists. Yes, you should have posted there. Yes, _someone_ was right to point that out to you so you know for next time. No, it's not a big deal if a few people on the list make a bigger deal out of it than seems necessary. Yes, your best bet is to just ignore the loudmouths -- they only make noise if fed. As usual, the subsequent traffic has far exceeded the original faux pas. I've been an active member of this mailing list since some time around 1998, I think. It's often frustrating to see the same issues come round again and again -- but I look on it as a good thing. It means there's constantly new blood coming in to FreeBSD -- it means the project is very much alive. -- Bill Moran http://www.potentialtech.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Test
Simon Chang wrote: > Hear, hear. > > Chris, please remember NOT to do this again. > > SC > > Yanno - I was just gonna let this go but it seems a simple "sorry" isn't good enough for some that simply don't feel as if life is complete without some sorta bitchin' Grow up, get a life, move on. It wont be the first time someone does this - and it certainly won't be the last - much less have the offender (me in this case) apologize for it... Apology ... rescinded -- Best regards, Chris Used with permission. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Test
Hear, hear. Chris, please remember NOT to do this again. SC ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Test
Chris wrote: > Sorry folks - just testing something. > > Normally I would never reply to SPAM publicly, but it has to be publicized, at least once in a WHILE, that there is a list established for test messages, it's [EMAIL PROTECTED], and you should use that, NOT THIS LIST, never again. Believe it or not, there are some yoyos who actually subscribe to that list, and sometimes even complain about test mail there, so you have our public permission to electronically crap all over them when they do that. The test list is for testing, and you can do all you want to it with no limits, no permissions, no problems. So, please use it, not our public lists. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Test
Sorry folks - just testing something. -- Best regards, Chris No running on pool deck. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Fail to start KDE and Gnome - further test
--- Stephen Liu <[EMAIL PROTECTED]> wrote: > > --- Armin Pirkovitsch <[EMAIL PROTECTED]> wrote: > > > Stephen Liu wrote: > > [...] > > > > > > Something strange happened here. If copying "xorg.conf.new" on > > > /etc/X11/ and renaming it as "xorg.conf". I can't start X, the HD > > only > > > turning. Now I don't have /etc/X11/xorg.conf. I can start KDE > > (not > > > Gnome). I don't know which "xorg.conf" I am now running. > > > > just have a look at /var/log/Xorg.0.log - it will tell you which > > config > > file is used > > Hi Armin, > > > # cat /var/log/Xorg.0.log | grep xorg > (**) Option "XkbRules" "xorg" > (**) : XkbRules: "xorg" > > > # cat /var/log/Xorg.0.log | grep conf > Markers: (--) probed, (**) from config file, (==) default setting, > (EE) Unable to locate/open config file > Running "/usr/X11R6/bin/getconfig -X 6090 -I > /etc/X11,/usr/X11R6/etc/X11,/usr/X11R6/lib/modules,/usr/X > > 11R6/lib/X11/getconfig -v 0x10de -d 0x01df -r 0xa1 -s 0x1043 > -b 0x81f3 -c 0x0300" > (==) Using default built-in configuration (53 lines) > (==) --- Start of built-in configuration --- > (==) --- End of built-in configuration --- > Using the default mouse configuration. > Using the default keyboard configuration. > > Would it be "getconfig"? Why I'm not allowed to copy > /root/xorg.conf.ne /etc/X11/xorg and run xorg.conf there? > > Unfortunataely xorg.0.log is a big file. I have no idea where to > look > at the error message on running xorg.conf. Any suggestion? TIA > > > B.R. > satimis Hi Armin and folks, I made further test as follow; # cp /root/xorg.conf.new /etc/X11/xorg.conf Hard reboot X = [Ctrl]+[Alt]+[Back Space] exited to runlevel 3 Login : satimis Password: xxx $ startx KDE started with color looking strangely and finally PC hung. Hard reboot and removed xorg.conf # cat /var/log/Xorg.0.log . FreeFontPath:FPE "/usr/XR11R6/lib/X11/Fonts/misc/" refcount is 2. should be 1: fixing * end * Any advice how to fix this problem. TIA B.R. Stephen Liu Send instant messages to your online friends http://uk.messenger.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: test
On Mon, 26 Feb 2007 19:26:28 -0800 Bill Campbell wrote: >>Test Messages >>The lists freebsd-test, ..., ... have been created for test messages. >>Please use only these test lists for test messages. >>Do not send test messages to any of the normal lists. > If you do send test messages, at least put some humour in them :-). It would once again appear that common sense isn't all that common... Regards Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: test
On Mon, Feb 26, 2007, Warren Block wrote: >On Tue, 27 Feb 2007, Greg 'groggy' Lehey wrote: > >>On Friday, 23 February 2007 at 22:46:40 -, Justin Schlingmann wrote: >>>Lets see if the mailserver can find my hostname from 80.126.252.242 >> >>I think we're going to have to put this in the charter: please do >>*not* send "test" messages to tens of thousands of people when you >>just want to test your own configuration. We have a mailing list >>[EMAIL PROTECTED] exactly for that purpose. > >A notice on the web page here might help: > >http://www.freebsd.org/community/mailinglists.html > >With it between the Mailing List Archives and English Mailing Lists >sections, saying something like: > >Test Messages > >The lists freebsd-test, ..., ... have been created for test messages. >Please use only these test lists for test messages. > >Do not send test messages to any of the normal lists. If you do send test messages, at least put some humour in them :-). Bill -- INTERNET: [EMAIL PROTECTED] Bill Campbell; Celestial Software LLC URL: http://www.celestial.com/ PO Box 820; 6641 E. Mercer Way FAX:(206) 232-9186 Mercer Island, WA 98040-0820; (206) 236-1676 ``The Income Tax has made more Liars out of American people than Golf has.'' Will Rogers ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: test
On Tue, 27 Feb 2007, Greg 'groggy' Lehey wrote: On Friday, 23 February 2007 at 22:46:40 -, Justin Schlingmann wrote: Lets see if the mailserver can find my hostname from 80.126.252.242 I think we're going to have to put this in the charter: please do *not* send "test" messages to tens of thousands of people when you just want to test your own configuration. We have a mailing list [EMAIL PROTECTED] exactly for that purpose. A notice on the web page here might help: http://www.freebsd.org/community/mailinglists.html With it between the Mailing List Archives and English Mailing Lists sections, saying something like: Test Messages The lists freebsd-test, ..., ... have been created for test messages. Please use only these test lists for test messages. Do not send test messages to any of the normal lists. -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: test
On Friday, 23 February 2007 at 22:46:40 -, Justin Schlingmann wrote: > Lets see if the mailserver can find my hostname from 80.126.252.242 I think we're going to have to put this in the charter: please do *not* send "test" messages to tens of thousands of people when you just want to test your own configuration. We have a mailing list [EMAIL PROTECTED] exactly for that purpose. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers. pgp5fV7xw5jMa.pgp Description: PGP signature
test
Lets see if the mailserver can find my hostname from 80.126.252.242 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Memory test
> -Original Message- > Subject: Memory test > > I need to checkout memory on a remote machine. I see there is memtest and > memtest86 out there. Which one is appropriate for my situation?: CPU is a > dual cpu, dual core SMP Intel Xeon. Can I run either program while the > machine is performing other tasks?** > > > -- > Yudhvir Singh Sidhu No, Memtest must be ran from the CD (e.g. boot of the CD) so that is not a good solution for a remote test. I don't know of any that can be run remotely. Regards, Russell Wood DISCLAIMER: Disclaimer. This e-mail is private and confidential. If you are not the intended recipient, please advise us by return e-mail immediately, and delete the e-mail and any attachments without using or disclosing the contents in any way. The views expressed in this e-mail are those of the author, and do not represent those of this company unless this is clearly indicated. You should scan this e-mail and any attachments for viruses. This company accepts no liability for any direct or indirect damage or loss resulting from the use of any attachments to this e-mail. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Memory test
I need to checkout memory on a remote machine. I see there is memtest and memtest86 out there. Which one is appropriate for my situation?: CPU is a dual cpu, dual core SMP Intel Xeon. Can I run either program while the machine is performing other tasks?** -- Yudhvir Singh Sidhu 408 375 3134 cell ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
test
Sorry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: sparc64 and perl 5.8.8 port test failures?
I tried deleting the work subdirectory and doing both a 'make' and 'make WITHOUT_PERL_64BITINT=yes' but make test still fails the same way on both the pack and integer tests .. is it possible that there is some misconfiguration in my system that is confusing the configure script w.r.t. 64bitness of my machine ? I guess I could start mucking with the config.sh by hand but I'd rather figure out why the port just doesn't work as is. steve. > - Original Message - > From: "David Landgren" <[EMAIL PROTECTED]> > To: "Steven D. Yee" <[EMAIL PROTECTED]> > Subject: Re: sparc64 and perl 5.8.8 port test failures? > Date: Wed, 03 Jan 2007 08:49:49 +0100 > > > Steven D. Yee wrote: > > I'm seeing multiple errors from make test and I can't seem to > > figure out how to get rid of them. As far as I can > > tell it builds correctly. > > [...] > > > ../lib/integer..NOK 10 > > # Failed test 'left shift' > > # in ../lib/integer.t at line 49. > > # got: '-4292583424' > > # expected: '-9223372036854775808' > > # Looks like you failed 1 test of 11. > > ../lib/integer..dubious > > Test returned status 1 (wstat 256, 0x100) > > DIED. FAILED test 10 > > Failed 1/11 tests, 90.91% okay > > > > > > I did try building with WITHOUT_PERL_64BITINT=yes but that didn't > > seem to make a difference, although its possible that I screwed that > > up since conf.sh still shows multiple references to 64 bit ints > > (even use64bitint is defined) > > > > does anyone have any pointers as to what may be going on? or > > where to start looking? > > This looks like the build is bringing in 64bitness when it > shouldn't (or vice versa). The build process might have remnants of > the previous config run lying around (in Policy.sh and/or > config.sh). Step down into the build directory and delete these two > files, and build again. > > Or, better yet, just delete the entire ./work directory, and build it again. > > Later, > DAvid > -- ___ Search for products and services at: http://search.mail.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: sparc64 and perl 5.8.8 port test failures?
Steven D. Yee wrote: I'm seeing multiple errors from make test and I can't seem to figure out how to get rid of them. As far as I can tell it builds correctly. [...] ../lib/integer..NOK 10 # Failed test 'left shift' # in ../lib/integer.t at line 49. # got: '-4292583424' # expected: '-9223372036854775808' # Looks like you failed 1 test of 11. ../lib/integer......dubious Test returned status 1 (wstat 256, 0x100) DIED. FAILED test 10 Failed 1/11 tests, 90.91% okay I did try building with WITHOUT_PERL_64BITINT=yes but that didn't seem to make a difference, although its possible that I screwed that up since conf.sh still shows multiple references to 64 bit ints (even use64bitint is defined) does anyone have any pointers as to what may be going on? or where to start looking? This looks like the build is bringing in 64bitness when it shouldn't (or vice versa). The build process might have remnants of the previous config run lying around (in Policy.sh and/or config.sh). Step down into the build directory and delete these two files, and build again. Or, better yet, just delete the entire ./work directory, and build it again. Later, DAvid ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: sparc64 and perl 5.8.8 port test failures?
Steven D. Yee wrote: I'm seeing multiple errors from make test and I can't seem to figure out how to get rid of them. As far as I can tell it builds correctly. [...] ../lib/integer..NOK 10 # Failed test 'left shift' # in ../lib/integer.t at line 49. # got: '-4292583424' # expected: '-9223372036854775808' # Looks like you failed 1 test of 11. ../lib/integer......dubious Test returned status 1 (wstat 256, 0x100) DIED. FAILED test 10 Failed 1/11 tests, 90.91% okay I did try building with WITHOUT_PERL_64BITINT=yes but that didn't seem to make a difference, although its possible that I screwed that up since conf.sh still shows multiple references to 64 bit ints (even use64bitint is defined) does anyone have any pointers as to what may be going on? or where to start looking? This looks like the build is bringing in 64bitness when it shouldn't (or vice versa). The build process might have remnants of the previous config run lying around (in Policy.sh and/or config.sh). Step down into the build directory and delete these two files, and build again. Or, better yet, just delete the entire ./work directory, and build it again. Later, DAvid ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
sparc64 and perl 5.8.8 port test failures?
I'm seeing multiple errors from make test and I can't seem to figure out how to get rid of them. As far as I can tell it builds correctly. The errors look like: ... t/op/pack.# Failed at op/pack.t line 631 # Failed at op/pack.t line 631 FAILED at test 514 ... lib/integer...# Failed test 'left shift' # in ../lib/integer.t at line 49. # got: '-4292583424' # expected: '-9223372036854775808' FAILED at test 10 running harness directly gives a bit more information: ... op/pack.ok 1/13864# Failed at op/pack.t line 631 # Failed at op/pack.t line 631 # Failed at op/pack.t line 631 op/pack.ok 108/13864# Failed at op/pack.t line 631 # Failed at op/pack.t line 631 # Failed at op/pack.t line 631 # Failed at op/pack.t line 631 op/pack.NOK 1284# Failed at op/pack.t line 631 # Failed at op/pack.t line 631 op/pack.ok 11275/13864# Failed at op/pack.t line 631 op/pack.FAILED tests 514, 624, 954, 1284, 1614, 1944, 2274, 3374, 3429, 13057 Failed 10/13864 tests, 99.93% okay ... ../lib/integer..NOK 10 # Failed test 'left shift' # in ../lib/integer.t at line 49. # got: '-4292583424' # expected: '-9223372036854775808' # Looks like you failed 1 test of 11. ../lib/integer..dubious Test returned status 1 (wstat 256, 0x100) DIED. FAILED test 10 Failed 1/11 tests, 90.91% okay I did try building with WITHOUT_PERL_64BITINT=yes but that didn't seem to make a difference, although its possible that I screwed that up since conf.sh still shows multiple references to 64 bit ints (even use64bitint is defined) does anyone have any pointers as to what may be going on? or where to start looking? Sparc Ultra2 2GB memory Freebsd 6.1-RELEASE-p11 steve. -- ___ Search for products and services at: http://search.mail.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: shell test for stdout=stderr
Matthew Seaman wrote:
Robin Becker wrote:
Is there a way for a shell script to test if 2> is the same as 1>? I
want to put messages in both when they are connected to different files,
but would like to avoid duplicating the message when they are the same.
You could try using fstat(1) to print out the open file descriptors from
your process:
fstat -p $$
and then compare the values in the DEV and INUM columns -- unfortunately
fstat has no way to map back from those device and inode values to
filenames.
thanks for the fstat tip
this code seems to do what I want
fstat -p $$ | awk '{if($4=="1"||$4=="2"){F[$4]=$5+$6+$8}}
END{
if(F["1"]==F["2"]) print 1
}'
I suppose there might be a problem if F never gets created or one of 1/2
were closed prior to execution. I probably need a BEGIN{F[""]=""} or
something to make it a bit more robust.
--
Robin Becker
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: shell test for stdout=stderr
Robin Becker wrote: > Is there a way for a shell script to test if 2> is the same as 1>? I > want to put messages in both when they are connected to different files, > but would like to avoid duplicating the message when they are the same. You could try using fstat(1) to print out the open file descriptors from your process: fstat -p $$ and then compare the values in the DEV and INUM columns -- unfortunately fstat has no way to map back from those device and inode values to filenames. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
shell test for stdout=stderr
Is there a way for a shell script to test if 2> is the same as 1>? I want to put messages in both when they are connected to different files, but would like to avoid duplicating the message when they are the same. -- Robin Becker ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: test please delete
On Thu, 12 Oct 2006, Josef Grosch wrote: -- Josef Grosch | Another day closer to a | FreeBSD 6.1 [EMAIL PROTECTED] | Micro$oft free world | Berkeley, Ca. Please use the test mailing list: http://lists.freebsd.org/mailman/listinfo/freebsd-test Regards, Uli. Peter Ulrich Kruppa Wuppertal Germany ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
test please delete
-- Josef Grosch | Another day closer to a | FreeBSD 6.1 [EMAIL PROTECTED] | Micro$oft free world | Berkeley, Ca. pgpclfgwfCiFQ.pgp Description: PGP signature
test
testing newserver: news.myown.framed.net ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Any idea how to stress test our bandwidth?
Your client has major flaw in their test plan. Just because they have large bandwidth to you does not mean the public websites that want to test with also have that size bandwidth. So any time they test loading up targeting some public website they will be limited to some portion of the targeted website max bandwidth. Both sending and receiving sites must have same bandwidth for their test plan to have meaning. Like when client tests with you who is their ISP. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of jay alvarez Sent: Friday, August 11, 2006 4:02 AM To: freebsd-questions@freebsd.org Subject: Any idea how to stress test our bandwidth? I hope you don't mind my asking this here. I'm working in an ISP right now. We are using mrtg for each client connected to us. They can view their mrtg statistics. Their way to the internet is to us. Say a client connects to us via E1, they are guaranteed of 2.048Mbps because our uplink to the Internet is more than the total of all the clients link's bandwidth that are connected to us. Now one client wants to make sure that they will be able to reach their guaranteed bandwidth through the mrtg graphs. If we transfer huge data from their site only up to us, we can theoretically stress out their bandwidth. However, they want to try increasing their consumption and see for their self if they will reach the desired bandwidth if they are actually connecting to any site in the Internet, outside our network. Running iperf from their site to us doesn't seem to reflect to the MRTG. Any idea how to explain this to our client? Thank you very much for your help -JaY __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Any idea how to stress test our bandwidth?
Maybe this helps... http://www.netperf.org/netperf/NetperfPage.html Bob On Fri, 2006-08-11 at 01:01 -0700, jay alvarez wrote: > I hope you don't mind my asking this here. > > I'm working in an ISP right now. We are using mrtg for > each client connected to us. They can view their mrtg > statistics. Their way to the internet is to us. Say a > client connects to us via E1, they are guaranteed of > 2.048Mbps because our uplink to the Internet is more > than the total of all the clients link's bandwidth > that are connected to us. Now one client wants to make > sure that they will be able to reach their guaranteed > bandwidth through the mrtg graphs. If we transfer huge > data from their site only up to us, we can > theoretically stress out their bandwidth. However, > they want to try increasing their consumption and see > for their self if they will reach the desired > bandwidth if they are actually connecting to any site > in the Internet, outside our network. Running iperf > from their site to us doesn't seem to reflect to the > MRTG. Any idea how to explain this to our client? > > > Thank you very much for your help > -JaY > > > __ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Any idea how to stress test our bandwidth?
I hope you don't mind my asking this here. I'm working in an ISP right now. We are using mrtg for each client connected to us. They can view their mrtg statistics. Their way to the internet is to us. Say a client connects to us via E1, they are guaranteed of 2.048Mbps because our uplink to the Internet is more than the total of all the clients link's bandwidth that are connected to us. Now one client wants to make sure that they will be able to reach their guaranteed bandwidth through the mrtg graphs. If we transfer huge data from their site only up to us, we can theoretically stress out their bandwidth. However, they want to try increasing their consumption and see for their self if they will reach the desired bandwidth if they are actually connecting to any site in the Internet, outside our network. Running iperf from their site to us doesn't seem to reflect to the MRTG. Any idea how to explain this to our client? Thank you very much for your help -JaY __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: memtest86 & memory test
"FreeBSD Daemon" <[EMAIL PROTECTED]> writes: > Is there a memory test suite other them memtest86/memtest86+ There are others in the ports, but they aren't nearly as effective. Of course, if you really want "effective," there is no substitute for a dedicated device... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: memtest86 & memory test
Hi,
I think memtest86 is the best, but you could use something like
this bellow. Just adjust the value of N_MEGABYTES, and start as many
process as you want to full the fisical memory.
[start of code]
#include
#define N_MEGABYTES 160
#define TOTAL (N_MEGABYTES * 1024 * 1024)
int main(void)
{
int i;
char *p;
char *mem = malloc(TOTAL);
if ( mem == NULL )
{
perror("malloc");
return 1;
}
while ( 1 )
{
for (i = 0, p = mem; i < TOTAL; i++, p++)
{
if ( *p == 0 )
*p = 1;
*p <<= 1;
}
}
return 0;
}
[end of code]
On Wed, 19 Apr 2006, FreeBSD Daemon wrote:
|Dear list
|
|Is there a memory test suite other them memtest86/memtest86+
|
|TIA
|
|zheyu
|
|___
|freebsd-questions@freebsd.org mailing list
|http://lists.freebsd.org/mailman/listinfo/freebsd-questions
|To unsubscribe, send any mail to "[EMAIL PROTECTED]"
|
- Marcelo
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
memtest86 & memory test
Dear list Is there a memory test suite other them memtest86/memtest86+ TIA zheyu ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How do I test disk performance in Freebsd60 ?
On Wed, 22 Mar 2006 13:32:29 +0200 "Halid Faith" <[EMAIL PROTECTED]> wrote: > I use FreeBSD60 on Dell1600 SC ( 2gbyte Ram 4 CPU ) > amr0: mem 0xfcc0-0xfcc0 irq 21 at > device 2.0 on pci2 > amr0: Firmware 351X, BIOS 1.10, 64MB RAM > > I have 3 scsi disks that each about 70 Gbyte based RAID5. That is > Total capacity nearly 140 Gbyte. > > > I want to test disk / cd /usr/ports ; make search info=performance should give you some tools (bonnie, from memory) > raid card. ... other than setup raid, yank the cable in one/several of the drives and see what happens? Beto ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
How do I test disk performance in Freebsd60 ?
I use FreeBSD60 on Dell1600 SC ( 2gbyte Ram 4 CPU ) amr0: mem 0xfcc0-0xfcc0 irq 21 at device 2.0 on pci2 amr0: Firmware 351X, BIOS 1.10, 64MB RAM I have 3 scsi disks that each about 70 Gbyte based RAID5. That is Total capacity nearly 140 Gbyte. I want to test disk / raid card. I tried below command 10 times while I 'm root date && dd if=/dev/zero of=deleteme.now bs=64k count=300 && rm deleteme.now && date 1 - 19660800 bytes transferred in 3.420916 secs (5747232 bytes/sec) 2 - 19660800 bytes transferred in 3.318186 secs (5925165 bytes/sec) 3 - 19660800 bytes transferred in 1.325308 secs (14834893 bytes/sec) 4 - 19660800 bytes transferred in 1.475633 secs (13323637 bytes/sec) 5 - 19660800 bytes transferred in 1.458992 secs (13475605 bytes/sec) 6 - 19660800 bytes transferred in 1.373914 secs (14310066 bytes/sec) 7 - 19660800 bytes transferred in 1.597467 secs (19307485 bytes/sec) 8 - 19660800 bytes transferred in 1.308806 secs (15021937 bytes/sec) 9 - 19660800 bytes transferred in 1.324031 secs (14849201 bytes/sec) 10- 19660800 bytes transferred in 1.438717 secs (13665510 bytes/sec) As you see the values of bytes/sec is not stable very changeable. I wonder Do disks or the raid card work properly ? Thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SATA Raid (stress test..)
he array controller and enabling the write cache on the disks. This is stupidly insane unless you've planned for the worsts. The worst case scenario would be that you corrupt the array into an unrepairable state and loose everything if you had a power failure. -- BSD Podcasts @ http://bsdtalk.blogspot.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" attach iozone result of amrd0 with 4 spindle Seagate Baracuda 300 Gb SATA II (1 hotspare) w/ Intel SRCS16 PCI-X Is that fast or what ? :) I'll have to take a closer look, but the first thing I noticed in your test report is that you are only using a 1MB test file. You should run a test that will also max out the on disk / controller buffers. I think the Baracuda's have a 16MB buffers (16MBx4=64MB) so try a 128MB test file. Also be nice to see more detailed hardware specs about the system and what version of FreeBSD are you running. Thanks. -- BSD Podcasts @ http://bsdtalk.blogspot.com/ . Second test with 128MB buffers (attach) on - SATA II Seagate Baracuda - PCI-X Intel SRCS16 - Intel Xeon 3.0 with 2 GB DDR RAM - and Intel SE7320EP2 board - FreeBSD-6.1 Pre-RELEASE Thanks before for good review and explanation. I need to be sure that there is no performance issue before i put this machine into production. regards reza ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SATA Raid (stress test..)
t I'm insane enough to run a production server with the > write-back cache policy enabled on the array controller and enabling the > write cache on the disks. This is stupidly insane unless you've planned for > the worsts. The worst case scenario would be that you corrupt the array into > an unrepairable state and loose everything if you had a power failure. -- > BSD Podcasts @ http://bsdtalk.blogspot.com/ > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" > attach iozone result of amrd0 with 4 spindle Seagate Baracuda 300 Gb SATA II > (1 hotspare) > w/ Intel SRCS16 PCI-X > Is that fast or what ? :) > I'll have to take a closer look, but the first thing I noticed in your test report is that you are only using a 1MB test file. You should run a test that will also max out the on disk / controller buffers. I think the Baracuda's have a 16MB buffers (16MBx4=64MB) so try a 128MB test file. Also be nice to see more detailed hardware specs about the system and what version of FreeBSD are you running. Thanks. -- BSD Podcasts @ http://bsdtalk.blogspot.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SATA Raid (stress test..)
Nikolas Britton wrote: On 3/3/06, Alex Zbyslaw <[EMAIL PROTECTED]> wrote: Nikolas Britton wrote: Please can you be careful when you attribute your comments. You've sent this email "to" me, and left only my name in the attributions as if I were someone suggesting either dd or diskinfo as accurate benchmarks, when in fact my contribution was to suggest unixbench and sandra-lite. Maybe you hate those too, in which case you can quote what I said in-context and rubbish that at your pleasure. Yes I see your point, it does look like I'm replying to something you wrote. This was a oversight and I am sorry. OK. Remember that 105MB/s number I quoted above?, that's just the sustained read transfer rate for a big ass file, I don't need to work with big ass files. I need to work with 15MB files (+/- 5MB). After buying the right disks, controller, mainboard etc. and lots of tuning with the help of iozone I get: 200 - 350MB/s overall (read, write, etc.) for files less then or equal to 64MB*. So anyways, that's what iozone can do for you. google it and you'll find out more stuff about it. Thanks for the info. I think I can only dream about numbers like like yours. Iozone looks to be in the ports so I see some of my weekend disappearing looking at it :-) It runs on over two dozen operating systems, including windows. Their are two primary reasons I can get such high transfer rates from simple SATA drives. The first one was the selection of the mainboard that had a PCI-X slots, I built this system before PCI-Express mainboards and controllers hit the market. The PCI bus is severely restricted and obsolete, I'm simply going to post the theoretical maximum throughput in MB/s for the various bus standards: f(x,y) = x-bits * y-MHz / 8 = maximum theoretical throughput in MB/s PCI: 32 bits * 33 Mhz / 8 = 132 MB/s (standard PCI bus found on every pc) PCI: (32bits, 66MHz) = 264MB/s (Cards are commonplace, mainboards aren't) PCI-X: (64, 33) = 264MB/s (obsolete, won't find it on new boards.) PCI-X: (64, 66) = 528MB/s (Commonplace.) PCI-X: (64, 100) = 800 PCI-X: (64, 133) = 1064 (Commonplace.) PCI-X: (64, 266) = 2128 PCI-X: (64, 533) = 4264 (very hard to find, even on high-end equipment.) PCI-X version 1 (66MHz - 133MHz) and PCI-X version 2 (266MHz - 533MHz). PCI-X is backwards compatible with PCI and slower versions of PCI-X, for example you can put a standard PCI card in a PCI-X 533MHz slot and it will simply run at (32, 33) similarly a 66 MHz PCI card will run at (32, 66) and so on and so forth. PCI-X is also forwards compatible in the fact that you can run a 133MHz PCI-X card in a standard (32, 33) PCI slot. Because of the backwards and an forwards compatibly I feel that PCI-X is superior to PCI-Express, *BUT* PCI-Express moving forwards is far far superior to PCI & PCI-X because it does not have 13 years of legacy to remain compatible with, it's cheaper to produce, and it's already in lower-end desktop systems as a replacement for AGP thanks to all the gamers. A few years from now PCI will end up where ISA / EISA are. I'm veering way off topic so I will not go into anymore details about PCI, PCI-X, and PCI-Express. Google around for the shortcomings of PCI / PCI-X and why PCI-Express is the future. PCI-Express: PCIe is not compatible with PCI or PCI-X (except for PCIe to PCI bridging) and it's just, well, totally different from the PCI spec and I'm already way off topic so again just google the details. It's theoretical maximums are expressed in Gigabits per second but I will convert them to MB/s for comparison with PCI and PCI-X. x1: 2.5Gbps = 312.5MB/s x2: 625MB/s x4: 1250MB/s x8: 2500MB/s x12: 3750MB/s x16: 5000MB/s x32: 1MB/s Anyways back on topic, what was the topic? Oh yes, why you won't see 200MB/s - 350MB/s if your using a standard PCI slot. If you look back up all the way at the top you will see that the standard PCI bus is a crap shoot and that it's limited to a theoretical maximum of 132 MB/s. What this means is that your RAID controller and the disks attached to it and the cache buffers attached to the disks are all capped at that theoretical maximum of 132MB/s. Then you have to take into account that the PCI bus is shared with other devices such as the network card, video card, USB, etc. Your RAID controller has to fight will all these devices and a 1Gbit NIC card can eat up 125MB/s (12.5MB/s for a 100Mbit NIC). The next reason for those high gains is because I picked drives with 16MB cache buffers and that I'm insane enough to run a production server with the write-back cache policy enabled on the array controller and enabling the write cache on the disks. This is stupidly insane unless you've planned for the worsts. The worst case scenario would be that you corrupt the array into an unrepairable state and loose everything if you had a power failure. -- BSD Podcasts @ http://bsdtalk.blogspot.com/ __
Re: SATA Raid (stress test..)
On 3/3/06, Alex Zbyslaw <[EMAIL PROTECTED]> wrote: > Nikolas Britton wrote: > > >>Please can you be careful when you attribute your comments. You've sent > >>this email "to" me, and left only my name in the attributions as if I > >>were someone suggesting either dd or diskinfo as accurate benchmarks, > >>when in fact my contribution was to suggest unixbench and sandra-lite. > >>Maybe you hate those too, in which case you can quote what I said > >>in-context and rubbish that at your pleasure. > >> > >> > > > >Yes I see your point, it does look like I'm replying to something you > >wrote. This was a oversight and I am sorry. > > > > > OK. > > >Remember that 105MB/s number I quoted above?, that's just the > >sustained read transfer rate for a big ass file, I don't need to work > >with big ass files. I need to work with 15MB files (+/- 5MB). After > >buying the right disks, controller, mainboard etc. and lots of tuning > >with the help of iozone I get: 200 - 350MB/s overall (read, write, > >etc.) for files less then or equal to 64MB*. > > > >So anyways, that's what iozone can do for you. google it and you'll > >find out more stuff about it. > > > > > Thanks for the info. I think I can only dream about numbers like like > yours. Iozone looks to be in the ports so I see some of my weekend > disappearing looking at it :-) > It runs on over two dozen operating systems, including windows. Their are two primary reasons I can get such high transfer rates from simple SATA drives. The first one was the selection of the mainboard that had a PCI-X slots, I built this system before PCI-Express mainboards and controllers hit the market. The PCI bus is severely restricted and obsolete, I'm simply going to post the theoretical maximum throughput in MB/s for the various bus standards: f(x,y) = x-bits * y-MHz / 8 = maximum theoretical throughput in MB/s PCI: 32 bits * 33 Mhz / 8 = 132 MB/s (standard PCI bus found on every pc) PCI: (32bits, 66MHz) = 264MB/s (Cards are commonplace, mainboards aren't) PCI-X: (64, 33) = 264MB/s (obsolete, won't find it on new boards.) PCI-X: (64, 66) = 528MB/s (Commonplace.) PCI-X: (64, 100) = 800 PCI-X: (64, 133) = 1064 (Commonplace.) PCI-X: (64, 266) = 2128 PCI-X: (64, 533) = 4264 (very hard to find, even on high-end equipment.) PCI-X version 1 (66MHz - 133MHz) and PCI-X version 2 (266MHz - 533MHz). PCI-X is backwards compatible with PCI and slower versions of PCI-X, for example you can put a standard PCI card in a PCI-X 533MHz slot and it will simply run at (32, 33) similarly a 66 MHz PCI card will run at (32, 66) and so on and so forth. PCI-X is also forwards compatible in the fact that you can run a 133MHz PCI-X card in a standard (32, 33) PCI slot. Because of the backwards and an forwards compatibly I feel that PCI-X is superior to PCI-Express, *BUT* PCI-Express moving forwards is far far superior to PCI & PCI-X because it does not have 13 years of legacy to remain compatible with, it's cheaper to produce, and it's already in lower-end desktop systems as a replacement for AGP thanks to all the gamers. A few years from now PCI will end up where ISA / EISA are. I'm veering way off topic so I will not go into anymore details about PCI, PCI-X, and PCI-Express. Google around for the shortcomings of PCI / PCI-X and why PCI-Express is the future. PCI-Express: PCIe is not compatible with PCI or PCI-X (except for PCIe to PCI bridging) and it's just, well, totally different from the PCI spec and I'm already way off topic so again just google the details. It's theoretical maximums are expressed in Gigabits per second but I will convert them to MB/s for comparison with PCI and PCI-X. x1: 2.5Gbps = 312.5MB/s x2: 625MB/s x4: 1250MB/s x8: 2500MB/s x12: 3750MB/s x16: 5000MB/s x32: 1MB/s Anyways back on topic, what was the topic? Oh yes, why you won't see 200MB/s - 350MB/s if your using a standard PCI slot. If you look back up all the way at the top you will see that the standard PCI bus is a crap shoot and that it's limited to a theoretical maximum of 132 MB/s. What this means is that your RAID controller and the disks attached to it and the cache buffers attached to the disks are all capped at that theoretical maximum of 132MB/s. Then you have to take into account that the PCI bus is shared with other devices such as the network card, video card, USB, etc. Your RAID controller has to fight will all these devices and a 1Gbit NIC card can eat up 125MB/s (12.5MB/s for a 100Mbit NIC). The next reason for those high gains is because I picked drives with 16MB cache buffers and that I'm insane enough to run a production server with the write-back cache policy enabled on the array controller and enabling the write cache on the disks. This is stupidly insane unless you've planned for the worsts. The worst case scenario would be that you corrupt the array into an unrepairable state and loose everything if you had a power failure. -- BSD Podcasts @ http://bsdtalk.blogspot.com/ __
Re: SATA Raid (stress test..)
Nikolas Britton wrote: Please can you be careful when you attribute your comments. You've sent this email "to" me, and left only my name in the attributions as if I were someone suggesting either dd or diskinfo as accurate benchmarks, when in fact my contribution was to suggest unixbench and sandra-lite. Maybe you hate those too, in which case you can quote what I said in-context and rubbish that at your pleasure. Yes I see your point, it does look like I'm replying to something you wrote. This was a oversight and I am sorry. OK. Remember that 105MB/s number I quoted above?, that's just the sustained read transfer rate for a big ass file, I don't need to work with big ass files. I need to work with 15MB files (+/- 5MB). After buying the right disks, controller, mainboard etc. and lots of tuning with the help of iozone I get: 200 - 350MB/s overall (read, write, etc.) for files less then or equal to 64MB*. So anyways, that's what iozone can do for you. google it and you'll find out more stuff about it. Thanks for the info. I think I can only dream about numbers like like yours. Iozone looks to be in the ports so I see some of my weekend disappearing looking at it :-) Best, --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
