Re: Testing for false email freebsd.org
Hi, Reference: From: Al Plant n...@hdk5.net Date: Fri, 02 Nov 2012 13:17:17 -1000 Message-id: 5094547d.5030...@hdk5.net To: freebsd-t...@freebsd.org, freebsd-questions questi...@freebsd.org Al Plant wrote: Test Read list mandates. Cross posting is deprecated Send test mail only to t...@freebsd.org Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich http://berklix.com Reply below not above, like a play script. Indent old text with . Send plain text. Not: HTML, multipart/alternative, base64, quoted-printable. ___ 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: Testing ethernet interface status
On 04/01/10 14:21, Peter Steele wrote: What's the best what to test the status of an Ethernet interface programmatically? We've been using this code similar to this: struct ifmediareq ifmr; memset(ifmr, 0, sizeof(ifmr)); strcpy(ifmr.ifm_name, nfe0); ioctl(sockfd, SIOCGIFMEDIA, (caddr_t)ifmr) and then checking the value of ifmr.ifm_status IFM_ACTIVE. We've found that every once in a while this code will return a false positive, indicating that the interface has gone offline when in fact it has not. So, is there a more reliable call to test if an Ethernet interface has gone offline? I was going to suggest that you look at the ifconfig(8) source code, but then I did so myself - it looks like you're doing it pretty much exactly how they are. I've never noticed ifconfig(8) returning an incorrect value, not to say it's not possible. Are you sure that nothing is causing interface state resets? i.e. mismatched duplex/speed settings between the FreeBSD machine and the switch? Have you checked dmesg(8) for logs of interface state changes? You can also check the output of 'netstat -i' to check for interface errors. ___ 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: Testing ethernet interface status
I don't remember everything, but I used to do a program to do that.
You should also check ifmr.ifm_active value.
There was some strange behaviour (obviously normal, but unexpected when I
coded it), about up/down interfaces and plug or unplugged cables
and yep, ifconfig's doing it 'wrong' :)
Samuel Martín Moro
{EPITECH.} tek4
CamTrace S.A.S
On Thu, Apr 1, 2010 at 8:56 PM, Steve Polyack kor...@comcast.net wrote:
On 04/01/10 14:21, Peter Steele wrote:
What's the best what to test the status of an Ethernet interface
programmatically? We've been using this code similar to this:
struct ifmediareq ifmr;
memset(ifmr, 0, sizeof(ifmr));
strcpy(ifmr.ifm_name, nfe0);
ioctl(sockfd, SIOCGIFMEDIA, (caddr_t)ifmr)
and then checking the value of ifmr.ifm_status IFM_ACTIVE. We've found
that every once in a while this code will return a false positive,
indicating that the interface has gone offline when in fact it has not.
So, is there a more reliable call to test if an Ethernet interface has
gone offline?
I was going to suggest that you look at the ifconfig(8) source code, but
then I did so myself - it looks like you're doing it pretty much exactly how
they are. I've never noticed ifconfig(8) returning an incorrect value, not
to say it's not possible.
Are you sure that nothing is causing interface state resets? i.e.
mismatched duplex/speed settings between the FreeBSD machine and the switch?
Have you checked dmesg(8) for logs of interface state changes? You can
also check the output of 'netstat -i' to check for interface errors.
___
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
___
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: Testing ethernet interface status
I was going to suggest that you look at the ifconfig(8) source code, but then I did so myself - it looks like you're doing it pretty much exactly how they are. I've never noticed ifconfig(8) returning an incorrect value, not to say it's not possible. Are you sure that nothing is causing interface state resets? i.e. mismatched duplex/speed settings between the FreeBSD machine and the switch? Have you checked dmesg(8) for logs of interface state changes? You can also check the output of 'netstat -i' to check for interface errors. I should have added that when our own monitoring code flags one of these false positives, there is no entry in /var/log/messages indicating that the nic has gone offine. I added a second call to confirm that indeed the interface is offline, and this second check seems to have largely solved the problem, but we have seen a case where even two consecutive checks return false positives. Maybe we need three tests? ___ 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: Testing - my emails don't seem to be getting through
On Wed, Oct 15, 2008 at 10:24:27AM +1000, Da Rock wrote: I've been getting a lot of rejections: Helo command rejected: Host not found (in reply to RCPT TO command). So now I'm running a test to see if this one will get through. I do not know why on earth you are testing this crap using a public mailing list, rather than mailing an account at Gmail or Hotmail or some such. Sorry to sound sour about it, but it's rude. The error you're receiving would be because your mail server during the SMTP handshake is saying HELO i.am.bob and the remote SMTP server attempts to resolve i.am.bob but cannot. By i.am.bob, I *literally* mean i.am.bob. If you're forwarding mail around on a private network on your LAN, your computer probably thinks its hostname is myfreebsdbox.my.lan, which isn't a publicly-resolvable hostname. There are ways in sendmail and postfix to solve this problem. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Testing - my emails don't seem to be getting through
On Wed, Oct 15, 2008 at 04:12:55AM -0700, Jeremy Chadwick wrote: On Wed, Oct 15, 2008 at 10:24:27AM +1000, Da Rock wrote: I've been getting a lot of rejections: Helo command rejected: Host not found (in reply to RCPT TO command). So now I'm running a test to see if this one will get through. I do not know why on earth you are testing this crap using a public mailing list, rather than mailing an account at Gmail or Hotmail or some such. Sorry to sound sour about it, but it's rude. Maybe he's testing it on a public mailing list because his Gmail or Hotmail (or whatever) account doesn't reject his emails, but the public mailing list does. I think the correct response here would have been to direct him to the freebsd-test mailing list: http://lists.freebsd.org/mailman/listinfo/freebsd-test -- Chad Perrin [ content licensed PDL: http://pdl.apotheon.org ] A: It reverses the normal flow of conversation. Q: What's wrong with top-posting? pgpMiJHFea9G5.pgp Description: PGP signature
Re: testing
Michael P. Soulier [EMAIL PROTECTED] wrote: I've gotten many bounces from the list MX lately. Let me test right from gmail instead of my ISP's mail server. From the Handbook: 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. % dig +short MX digitaltorque.ca 20 gatekeeper.digitaltorque.ca. 0 mail.digitaltorque.ca. I know those are the incoming MXs for your domain, but were you by any chance trying to relay to the FreeBSD list via gatekeeper? Its IP is listed on multiple RBLs: dnsbl.sorbs.net dul.dnsbl.sorbs.net zen.spamhaus.org -- 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]
Re: Testing RAM
On Sat, Jun 14, 2008 at 09:45:20AM -0500, Ryan Coleman wrote: As you've probably read in my previous posts I'm having issues, most likely with the RAM. How would I go about slamming the RAM in testing? I was figuring I'd drop from 4GB to 1GB and just push the board with the same cp -rvn commands I've been running in an attempt to populate my 7TB RAID5. Use sysutils/memtest86 Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpIDoDabLHqF.pgp Description: PGP signature
RE: Testing RAM
Ryan Coleman wrote: How would I go about slamming the RAM in testing? I use Memtest86 to test memory: http://www.memtest86.com/ HTH, David ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Testing RAM
On Sat, 14 Jun 2008 09:45:20 -0500 Ryan Coleman [EMAIL PROTECTED] wrote: How would I go about slamming the RAM in testing? I was figuring I'd drop from 4GB to 1GB and just push the board with the same cp -rvn commands I've been running in an attempt to populate my 7TB RAID5. Also, am I using the wrong FS for the RAID? I partitioned it with gpt (1 large slice) and formatted it with newfs but is there another way? A better way? I read about ZFS recently but I am sure the speed of reading from a RAID5 is lost with it's redundancies. For something that large, ZFS would be my choice. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Testing RAM
Zane C.B. wrote: On Sat, 14 Jun 2008 09:45:20 -0500 Ryan Coleman [EMAIL PROTECTED] wrote: How would I go about slamming the RAM in testing? I was figuring I'd drop from 4GB to 1GB and just push the board with the same cp -rvn commands I've been running in an attempt to populate my 7TB RAID5. Also, am I using the wrong FS for the RAID? I partitioned it with gpt (1 large slice) and formatted it with newfs but is there another way? A better way? I read about ZFS recently but I am sure the speed of reading from a RAID5 is lost with it's redundancies. For something that large, ZFS would be my choice I take it that's not something I can do after the fact, right? I am not looking forward to redoing 1.6TB in file copying a second time ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Testing RAM
On Sat, 14 Jun 2008 17:11:32 -0500 Ryan Coleman [EMAIL PROTECTED] wrote: Zane C.B. wrote: On Sat, 14 Jun 2008 09:45:20 -0500 Ryan Coleman [EMAIL PROTECTED] wrote: How would I go about slamming the RAM in testing? I was figuring I'd drop from 4GB to 1GB and just push the board with the same cp -rvn commands I've been running in an attempt to populate my 7TB RAID5. Also, am I using the wrong FS for the RAID? I partitioned it with gpt (1 large slice) and formatted it with newfs but is there another way? A better way? I read about ZFS recently but I am sure the speed of reading from a RAID5 is lost with it's redundancies. For something that large, ZFS would be my choice I take it that's not something I can do after the fact, right? I am not looking forward to redoing 1.6TB in file copying a second time Not that I am aware of. My big reason I would go with ZFS is it would make future updates easier as you can do it on the fly if the disks are just being added to a system. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Testing RAM
Zane C.B. wrote: On Sat, 14 Jun 2008 17:11:32 -0500 Ryan Coleman [EMAIL PROTECTED] wrote: Zane C.B. wrote: On Sat, 14 Jun 2008 09:45:20 -0500 Ryan Coleman [EMAIL PROTECTED] wrote: How would I go about slamming the RAM in testing? I was figuring I'd drop from 4GB to 1GB and just push the board with the same cp -rvn commands I've been running in an attempt to populate my 7TB RAID5. Also, am I using the wrong FS for the RAID? I partitioned it with gpt (1 large slice) and formatted it with newfs but is there another way? A better way? I read about ZFS recently but I am sure the speed of reading from a RAID5 is lost with it's redundancies. For something that large, ZFS would be my choice I take it that's not something I can do after the fact, right? I am not looking forward to redoing 1.6TB in file copying a second time Not that I am aware of. My big reason I would go with ZFS is it would make future updates easier as you can do it on the fly if the disks are just being added to a system. Ok, and since I have all 8 ports used on this SATA RAID controller I won't worry about it. I reinstalled 6.3-RELEASE for amd64 and I cannot get the DNS client to work... I can do one lookup and then it stops working. I am so frustrated. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: testing from sage|ns1.thought.org
On Thu, Jan 03, 2008 at 02:27:53PM -0800, Gary Kline wrote: Let's see ifthis gets out.. Let's see if you can use [EMAIL PROTECTED] in the future. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: testing for directory
On Sun, Apr 29, 2007 at 04:39:42PM -0400, Robert Huff wrote: In C code, is there a quick and dirty way to tell if a path points to a directory? Or do I have to open the parent directory and check the entry for that name? Try opening the path in question for writing with open(2). If it returns -1, and errno is EISDIR, it is a directory. This will be inconclusive on a read-only filesystem, or if the limit of open file handles is reached, or for any other reason that can make open(2) fail. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgp82o0Z9g4ES.pgp Description: PGP signature
Re: testing for directory
On Sunday 29 April 2007 15:58:48 Roland Smith wrote: On Sun, Apr 29, 2007 at 04:39:42PM -0400, Robert Huff wrote: In C code, is there a quick and dirty way to tell if a path points to a directory? Or do I have to open the parent directory and check the entry for that name? Just open() the path, then pass the fd to getdirentries(), if it returns -1, and errno = EINVAL, it's not a directory. (man getdirentries for more info) hth... don Try opening the path in question for writing with open(2). If it returns -1, and errno is EISDIR, it is a directory. This will be inconclusive on a read-only filesystem, or if the limit of open file handles is reached, or for any other reason that can make open(2) fail. Roland -- Don Hinton don.hinton at vanderbilt.edu or hintonda at gmail.com Institute for Software Integrated Systems (ISIS), Vanderbilt University tel: 615.480.5667 or 615.870.9728 pgpCl51TDL7hA.pgp Description: PGP signature
Re: testing for directory
On Apr 29, 2007, at 3:39 PM, Robert Huff wrote: In C code, is there a quick and dirty way to tell if a path points to a directory? man 2 stat Cheers, -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 [EMAIL PROTECTED]
Re: testing for directory
Jeffrey Goldberg writes: In C code, is there a quick and dirty way to tell if a path points to a directory? man 2 stat This, I believe, will be the answer I'm looking for. Thank you. 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: Testing firewire
On Sun, 12 Nov 2006, David Kelly wrote: On Nov 12, 2006, at 5:03 PM, Erik Norgaard wrote: So I thought: Is this like ethernet that I need a crossed cable or can I connect the two with an ordinary cable and check that it works? There is no master nor slave in Firewire, all are peers, and all have (essentially) the same socket. If the cable fits, it works. Witness the difference between a hardware standard driven by Apple (Firewire) and one from Intel/Microsoft (USB). Apple computers can be booted in target mode where the machine becomes nothing more than a Firewire hard drive. Only works for the primary drive, but works well. Apple recommends this mode (and Migration Assistant) for cloning user data and applications from one Mac to another. You might also try fwe(4) if your other OS's are capable of doing IP over firewire. fwe(4) emulates an ethernet interface and is a non-standard method of making Firewire become a network interface. If would work with other BSDs? or Mac OS/X? possibly. fwip(4) is what Windows and a lot of other operating systems use to accomplish this feat. Last I check, it was no in the generic kernel and had to be compiled in, specified in the loader.conf(5), or loaded with kldload(8). #device fwe # Ethernet over FireWire (non-standard!) #device fwip# IP over FireWire I had the fwip driver working with a Windows XP box for a little while. It worked fairly well, but I don't think it was really any faster than ethernet (at least for what I was doign with it). Hope this helps. George Fazio N3GQF mailto:[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: Testing firewire
David Kelly wrote: On Nov 12, 2006, at 5:03 PM, Erik Norgaard wrote: So I thought: Is this like ethernet that I need a crossed cable or can I connect the two with an ordinary cable and check that it works? There is no master nor slave in Firewire, all are peers, and all have (essentially) the same socket. If the cable fits, it works. Witness the difference between a hardware standard driven by Apple (Firewire) and one from Intel/Microsoft (USB). You might also try fwe(4) if your other OS's are capable of doing IP over firewire. Thanks, both run FreeBSD and I was thinking of trying fwe. I just don't know enough to feel certain I wouldn't short circuit and fry both devices if I connected them with a standard cable. Cheers, Erik -- Ph: +34.666334818 web: http://www.locolomo.org X.509 Certificate: http://www.locolomo.org/crt/8D03551FFCE04F0C.crt Key ID: 69:79:B8:2C:E3:8F:E7:BE:5D:C3:C3:B1:74:62:B8:3F:9F:1F:69:B9 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Testing firewire
David Kelly wrote: On Nov 12, 2006, at 5:03 PM, Erik Norgaard wrote: So I thought: Is this like ethernet that I need a crossed cable or can I connect the two with an ordinary cable and check that it works? There is no master nor slave in Firewire, all are peers, and all have (essentially) the same socket. If the cable fits, it works. Witness the difference between a hardware standard driven by Apple (Firewire) and one from Intel/Microsoft (USB). You might also try fwe(4) if your other OS's are capable of doing IP over firewire. OK, so I tried, and what can I deduce from this: I configured fwe0 on both and pinged from A to B, no response was received: B crashed (ok, so I assume this means it doesn't work). Interestingly, this one has a Ricoh R5C552 chipset which should be supported. But, it could be a conflict on the PCI-Cardbus bridge with the same IRQ? On A, this output appeared in dmesg: fwohci0: BUS reset fwohci0: node_id=0xc000ffc1, gen=3, CYCLEMASTER mode firewire0: 2 nodes, maxhop = 1, cable IRM = 1 (me) firewire0: bus manager 1 (me) fwohci0: BUS reset fwohci0: node_id=0x8000ffc0, gen=4, non CYCLEMASTER mode firewire0: 2 nodes, maxhop = 1, cable IRM = 1 firewire0: bus manager 1 firewire0: New S400 device ID:00e0180003094339 fwohci0: BUS reset fwohci0: node_id=0xc000ffc0, gen=5, CYCLEMASTER mode firewire0: 1 nodes, maxhop = 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) Does this mean it works? (the last 4 lines appeared after the other machine crashed). The interesting thing is that this one has a Texas Instruments PCI7x20 1394a-2000 OHCI Two-Port PHY/Link-Layer Controller, attached to a Texas Instruments PCI7420 FireWire + CardBuss bridge. None are on the hardware list (R6.1). The bridge also have a Texas Instruments PCI7420/PCI7620 Dual Socket CardBus and Smart Card Cont. w/ 1394a-2000 OHCI Two-Port PHY/Link-Layer Cont. and SD/MS-Pro Sockets attached which doesn't work. I'd be happy if things work on A, as this is my new machine :) Thanks, Erik -- Ph: +34.666334818 web: http://www.locolomo.org X.509 Certificate: http://www.locolomo.org/crt/8D03551FFCE04F0C.crt Key ID: 69:79:B8:2C:E3:8F:E7:BE:5D:C3:C3:B1:74:62:B8:3F:9F:1F:69:B9 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Testing firewire
On Nov 12, 2006, at 5:03 PM, Erik Norgaard wrote: So I thought: Is this like ethernet that I need a crossed cable or can I connect the two with an ordinary cable and check that it works? There is no master nor slave in Firewire, all are peers, and all have (essentially) the same socket. If the cable fits, it works. Witness the difference between a hardware standard driven by Apple (Firewire) and one from Intel/Microsoft (USB). Apple computers can be booted in target mode where the machine becomes nothing more than a Firewire hard drive. Only works for the primary drive, but works well. Apple recommends this mode (and Migration Assistant) for cloning user data and applications from one Mac to another. You might also try fwe(4) if your other OS's are capable of doing IP over firewire. -- David Kelly N4HHE, [EMAIL PROTECTED] Whom computers would destroy, they must first drive mad. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Testing 6.x
On 3/25/06, Tim [EMAIL PROTECTED] wrote: hey I am downloading your newest version, I will keep you informed about any bugs they may come up. Also what I think could be added to make it better. hey thanks! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Testing a DHCP server without jeopardizing my IP configuration?
On 5/30/05, Rob [EMAIL PROTECTED] wrote: Is there a way to test the DHCP server, without running dhclient and thus without losing my FreeBSD system's IP configuration? I'm just throwing a random idea out here, I have no clue if it'd actually work, but what about putting an alias in your rc.conf and setting it to pull its IP from DHCP? -- -Tomas Quintero ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Testing a DHCP server without jeopardizing my IP configuration?
Is there a way to test the DHCP server, without running dhclient and thus without losing my FreeBSD system's IP configuration? Hi, try dhcping from ports (net/dhcping). Read carrefully man pages, the idea of operation was not clear at first look (for me :-) but it works. Bodlin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Testing/repairing IDE drive
On Thursday 31 March 2005 21:25, Olivier Nicole wrote: Hi Hi have an IDE drive (bit old) that is starting to develop bad blocks. Is there a tool to scan the disk and reassign/block (I don't care loosing some space on that disk) the bad bocks? Best regards, Olivier Most manufacturers have utilities on their website that you can download and put onto a floppy. Generally this floppy is bootable and will perform diagnostics on the drive. -- Thanks, Josh Paetzel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: testing
Branton, Chris wrote: Dear Folks, I would like to volunteer to be a tester for you. If you want more info on me, and how I use FreeBsd let me know. Here are some excellent resources on contributing to FreeBSD: http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/index.html http://www.freebsd.org/doc/en_US.ISO8859-1/articles/problem-reports/article.html -- Bill Moran Potential Technologies 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: Testing...NO CONTENTS...
On Wednesday, 28 May 2003 at 21:24:27 -0400, Xpression wrote: Please don't send test mail to the normal FreeBSD lists. It wastes a lot of money around the world. There's a special test list for this 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 pgp0.pgp Description: PGP signature
Re: Testing serial ports
On Fri, Jan 03, 2003 at 02:36:06AM -0500, Dragoncrest wrote: I've got a slight problem where I think that I've got a serial port that has failed on one of my machines. So I'm looking for the simplest way to test a serial port to see if it is in fact working. Thanks for the info. Do you have any external serial devices, like a modem? You could also use another computer and place a null modem cable between them. Then use a command like tip(1) or minicom from the ports to connect to the device. What evidence leads you to believe that the serial port is bad? You're positive that it's turned on in the BIOS? Does dmesg reveal any sio entries? Nathan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: testing memory speed
On Mon, 9 Dec 2002, David S. Jackson wrote: Is there a utility to test memory speed? I looked at memtest in ports, but it looks like that mainly tests for faulty memory. I did a websearch and found a command: dd /dev/zero /dev/null, but that doesn't seem to summarize the memory speed easily for me. Can anyone else give me a pointer to how to test my machine's memory speed? How can I find out whether a memory stick is compatable with an old box? The speed of the memory is a hardware issue. If you mismatch the speeds of your memory and your motherboard, then the board will either try and force the memory to run a the speed it wants, or the motherboard will drop it's bus speed down to match that of the memory. Either way, I don't think that software is able to tell you if a stick of memory should be running at the speed it is, because the software can only read what the motherboard is running at. My suggestion would be to just try the memory. If it doesn't work, you won't break anything. The worst case scenario is that the motherboard detects the wrong size of memory if the speed is mismatched, which should still be usable anyways. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
RE: testing memory speed
Some BIOS detect memory speed and size. Mine showed a mismatch in speed 100 on one and 133 on another. Changed to both 133 and did not really see a difference. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Jason Hunt Sent: Monday, December 09, 2002 10:08 PM To: David S. Jackson Cc: [EMAIL PROTECTED] Subject: Re: testing memory speed On Mon, 9 Dec 2002, David S. Jackson wrote: Is there a utility to test memory speed? I looked at memtest in ports, but it looks like that mainly tests for faulty memory. I did a websearch and found a command: dd /dev/zero /dev/null, but that doesn't seem to summarize the memory speed easily for me. Can anyone else give me a pointer to how to test my machine's memory speed? How can I find out whether a memory stick is compatable with an old box? The speed of the memory is a hardware issue. If you mismatch the speeds of your memory and your motherboard, then the board will either try and force the memory to run a the speed it wants, or the motherboard will drop it's bus speed down to match that of the memory. Either way, I don't think that software is able to tell you if a stick of memory should be running at the speed it is, because the software can only read what the motherboard is running at. My suggestion would be to just try the memory. If it doesn't work, you won't break anything. The worst case scenario is that the motherboard detects the wrong size of memory if the speed is mismatched, which should still be usable anyways. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: testing memory speed
On Wed, Dec 18, 2002 at 11:24:06PM -0700, Mike wrote: Some BIOS detect memory speed and size. Mine showed a mismatch in speed 100 on one and 133 on another. Changed to both 133 and did not really see a difference. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Jason Hunt Sent: Monday, December 09, 2002 10:08 PM To: David S. Jackson Cc: [EMAIL PROTECTED] Subject: Re: testing memory speed On Mon, 9 Dec 2002, David S. Jackson wrote: Is there a utility to test memory speed? I looked at memtest in ports, but it looks like that mainly tests for faulty memory. I did a websearch and found a command: dd /dev/zero /dev/null, but that doesn't seem to summarize the memory speed easily for me. Memtest does give an indication of speed. It appears for example from my use of it that DDR ram is about 50% faster than the ordinary stuff... As has been pointed out by another poster, it is not quite so cut and dried as the pure speed of your memory, bus speed etc comes into it. Anyway just get a 2nd mortgage on your house and buy some RIMM .. ho ho.. -- Regards Cliff Sarginson The Netherlands [ This mail has been checked as virus-free ] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
