RE: load > 1, no process using >10% CPU...?
On Wednesday, April 20, 2005 2:20 AM, Damian Gerow <> unleashed the infinite monkeys and produced: > Until the build failed. Now top /still/ isn't showing me much. systat -vm > is showing me at just under 100% User, with little to no disk activity. > > I'm a little fuzzy as to /how/ load is calculated, but why would my system > think that it's doing all kinds of work when ps, top, and systat can't > really tell me /what/ it's doing? The "load" is the number of active processes (the number of processes in the run queue). That's all it measures - not CPU load, disk I/O or anything else - purely the number of processes in the run queue. Load and processor usage aren't linked. If the processes are I/O bound (for example) then while the system load may be high, the actual CPU usage may well be low. Google produced http://www.teamquest.com/resources/gunther/ldavg1.shtml, which isn't a bad description of the load average, though heavily based on Linux. -- Rob | Oh my God! They killed init! You bastards! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: scsi card recommendation
No problems here so far. If there are problems with this toolset, would E Moore be so kind as to release sourcecode for these so that someone can make a ports package out of it (I'd do it)? Or are there any alternatives (that also happen to work on the AMR card used in the PE750) ? Rgds, Rutger On Apr 20, 2005, at 5:24, Doug Ambrisko wrote: Rutger Bevaart writes: | i've got about 15 Dell 1750, 1850 and 2850 boxes that use AMR-based SCSI | RAID controllers. i can manage these perfectly using emoore's port of the | amrcontrol and MEGAMGR tools, under 5.x only after adding the 4x-compat | ports package. Be very careful. Use of those utilities can result in random problems. I've had to remove all usage of any of that stuff from our systems. We've had other programs on the system core dump etc. :-( Doug A. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FreeBSD tuning(7) is largely out of date
I've been spending some time trying to determine some tuning issues w.r.t. moving to FreeBSD 5.*, and I've run into some frustrations. Perhaps the biggest one is that there is a severe lack of information on how to tune large systems in tuning(7) and/or the Handbook, parts of which seem to be direct from tuning(7). I've read numerous mailing list posts which say things like "See the tuning(7) man page and innumerable mailing lists posts" but the reality is that most of the mailing list posts do not serve as reasonable documentation. Let's take a small example of something like KVA_PAGES. Under 4.11, I read the "innumerable mailing lists posts" which suggested that the default of 256 could be bumped up to 384 or 512. Being conservative, I went to 384. The machine wouldn't boot. After much searching, I located *in* *the* *source* that if you're using PAE, KVA_PAGES needs to be multiplied by two. 768 got me what I needed. So, that brings me here: Is there someone around who is actually familiar with large system tuning and who might be willing to update the tuning info with a comprehensive set of items that are likely to need tweaking on larger servers? I'm not talking about "let's write a book." I'm talking more like "edit /sys/i386/conf/NOTES, fix KVA_PAGES to mention the PAE caveat, maybe elaborate just a tad more, and then stick a terse reference such as 'Changing the size of the kernel's virtual address space can be done via KVA_PAGES. See /sys/i386/conf/NOTES' into tuning(7)". Repeat for as many tunables as possible. Maybe add a few sentences about any common caveats or gotchas. I would just like to see the tunables all mentioned in tuning(7). A short paragraph about each would be heaven. I don't mind paying a qualified someone to do this if they can do a good job of it at a reasonable rate. Contact me off-list if interested. Thanks. ... JG -- Joe Greco - sol.net Network Services - Milwaukee, WI - http://www.sol.net "We call it the 'one bite at the apple' rule. Give me one chance [and] then I won't contact you again." - Direct Marketing Ass'n position on e-mail spam(CNN) With 24 million small businesses in the US alone, that's way too many apples. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: scsi card recommendation
Rutger Bevaart writes: | i've got about 15 Dell 1750, 1850 and 2850 boxes that use AMR-based SCSI | RAID controllers. i can manage these perfectly using emoore's port of the | amrcontrol and MEGAMGR tools, under 5.x only after adding the 4x-compat | ports package. Be very careful. Use of those utilities can result in random problems. I've had to remove all usage of any of that stuff from our systems. We've had other programs on the system core dump etc. :-( Doug A. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: load > 1, no process using >10% CPU...?
Thus spake Dan Nelson ([EMAIL PROTECTED]) [19/04/05 22:13]: : > It turned out to be a runaway xmms process. But I still find it : > strange that it didn't show anything obvious in top. : : If xmms is threaded, you probably got bit by the "libpthread doesn't do : process CPU accounting" bug. Most threaded processes will just show up : as 0 %CPU in top, no matter what they're doing. The rusage stats are : handled correctly, though, so look for processes whose TIME value is : increasing at one (or more if you're SMP) seconds per second. That would be it, thanks. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: load > 1, no process using >10% CPU...?
On Tue, Apr 19, 2005 at 10:05:24PM -0400 I heard the voice of Damian Gerow, and lo! it spake thus: > > It turned out to be a runaway xmms process. But I still find it > strange that it didn't show anything obvious in top. Threaded processes don't rack up CPU%. It's an (annoying) side effect of the KSE-based threading libraries. There've been a few discussions about it, but last I heard there wasn't any concensus on how to fix it. -- Matthew Fuller (MF4839) | [EMAIL PROTECTED] Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: load > 1, no process using >10% CPU...?
In the last episode (Apr 19), Damian Gerow said: > Thus spake Damian Gerow ([EMAIL PROTECTED]) [19/04/05 21:21]: > : I'm a little fuzzy as to /how/ load is calculated, but why would my > : system think that it's doing all kinds of work when ps, top, and > : systat can't really tell me /what/ it's doing? > > It turned out to be a runaway xmms process. But I still find it > strange that it didn't show anything obvious in top. If xmms is threaded, you probably got bit by the "libpthread doesn't do process CPU accounting" bug. Most threaded processes will just show up as 0 %CPU in top, no matter what they're doing. The rusage stats are handled correctly, though, so look for processes whose TIME value is increasing at one (or more if you're SMP) seconds per second. -- Dan Nelson [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: load > 1, no process using >10% CPU...?
Thus spake Damian Gerow ([EMAIL PROTECTED]) [19/04/05 21:21]: : I'm a little fuzzy as to /how/ load is calculated, but why would my system : think that it's doing all kinds of work when ps, top, and systat can't : really tell me /what/ it's doing? It turned out to be a runaway xmms process. But I still find it strange that it didn't show anything obvious in top. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Please Suport Starsky2 DVB-S card please
On Tue, Apr 19, 2005 at 05:55:08PM +0300, Maher Mohamed wrote: > Hello there I would like to ask you if you could add to the final > realase drivers for the SkyStar2 PCI card it is a Digital Sat-Reciver > made by TechniSat Company, the bad thing though is that they do not > suport it The tricky part with many of these DVB cards is that often the vendor ship their drivers either completely in binary format, or for those who support Linux, in 'mostly' binary format. I have such a DVB card (by a different vendor) and it's unlikely that it would ever be supported without substantial reverse engineering (i.e. time), so I'll probably end up selling it. Regards, BMS ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
load > 1, no process using >10% CPU...?
I'm trying to compile editors/openoffice-2.0-devel (after successfully getting java/jdk15 running on amd64), and my load shot way up just as I started the compile. top didn't show me much, so I attributed it to the disk I/O that was going on, and didn't think much of it. Until the build failed. Now top /still/ isn't showing me much. systat -vm is showing me at just under 100% User, with little to no disk activity. I'm a little fuzzy as to /how/ load is calculated, but why would my system think that it's doing all kinds of work when ps, top, and systat can't really tell me /what/ it's doing? The system is AMD64 running 5.4-STABLE (compiled two nights ago, I believe). More information available on request... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: PXEBOOT/TFTPBOOT + big MD_ROOT problem
> Hi, > > I'm trying to make very big MD_ROOT (300MB) sent using PXEBOOT+TFTPBOOT. No > NFS. It's a sort of diskless machine with all the system on ram. There is a > problem when the preloaded image is >~32MB. Kernel loads but it does not > seem to find the files. It seems as if only part of the image is really > there. With a "small" image (<~32MB), no probleme. I use the same image, off > course, same init etc... just more data for my application in the big image > case. ... > Am I missing something obvious? I assume you saw this in the tftpd manual page? BUGS Files larger than 33488896 octets (65535 blocks) cannot be transferred without client and server supporting blocksize negotiation (RFC1783). Many tftp clients will not transfer files over 1678 octets (32767 blocks). -DG David G. Lawrence President Download Technologies, Inc. - http://www.downloadtech.com - (866) 399 8500 TeraSolutions, Inc. - http://www.terasolutions.com - (888) 346 7175 The FreeBSD Project - http://www.freebsd.org Pave the road of life with opportunities. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Newbie Question About System Update
On Tue, 19 Apr 2005 16:34:37 -0600 (MDT) Warner Losh <[EMAIL PROTECTED]> wrote: > From: Bill Moran <[EMAIL PROTECTED]> > Subject: Re: Newbie Question About System Update > Date: Tue, 19 Apr 2005 16:32:37 -0400 > > > Chuck Swiger <[EMAIL PROTECTED]> wrote: > > > Bill Moran wrote: > > > > The system can not replace programs that are in use, > > > > > > This is generally not the case. Unix lets you continue to access a file > > > after > > > it has been deleted, so long as the process hangs on to a file > > > descriptor. > > > This lets you replace programs in use, without running into the same > > > problems > > > that platforms like Windows have. > > > > What you say?: > > > > bash-2.05b$ su > > Password: > > bolivia# cp /usr/sbin/cron /home/wmoran/. > > bolivia# cp /home/wmoran/cron /usr/sbin/. > > cp: /usr/sbin/./cron: Text file busy > > bolivia# > > mv /usr/sbin/cron /usr/sbin/cron- > cp /blah/cron /usr/sbin/cron > > install does this behind the scenes. I suppose I have to stand corrected. Thanks for putting me straight. -- Bill Moran Potential Technologies http://www.potentialtech.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Newbie Question About System Update
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, Apr 19, 2005 at 04:32:54PM -0600, Warner Losh wrote: > (I don't think this original quote is Warner's, but I lost the poster's name somewhere) > > That being said, I quite often do installworld on running systems because I > > have no way to go to single-user mode. It almost always works well enough > > for my purposes, but I don't want anyone to think that it's "OK" to do this, > > as it's not guaranteed to work, and will most likely result in some programs > > not being updated (such as the examples in the previous paragraphs). > > It usually works well enough most of the time. I do it all the time > on my development machines. The problem is "well enough" and "most of > the time." > > Warner This is why, as I said, I test it on a sacrificial box--that box has almost identical hardware to the remote servers. I'm fortunate to have that setup though. - -- Scott Robbins PGP keyID EB3467D6 ( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 ) gpg --keyserver pgp.mit.edu --recv-keys EB3467D6 Anya: Listen, I have this little project I'm working on, and I heard you were the person to ask if... Willow: Yeah, that's me. Reliable dog-geyser-person. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCZYv2+lTVdes0Z9YRAu4XAKCWnpuYcpup0sAJLq0jwMBdsjyfRwCfatUE loSv7s/m8GWjVujZ++XIcQo= =oMwG -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Tuning for router performance
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] ("David Schwartz") writes:
>> options HZ=1000 #for polling
> That's too low. 2000 is the minimum you should consider.
This alone has helped.. now up to 200Kpps at least but my click
router has run out of puff since I haven't managed to get the
e1000 polling driver to load on it.
Anyone have any suggestions for other high performance packet
generator tools for this kind of testing?
-Paul-
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Newbie Question About System Update
From: Bill Moran <[EMAIL PROTECTED]> Subject: Re: Newbie Question About System Update Date: Tue, 19 Apr 2005 16:32:37 -0400 > Chuck Swiger <[EMAIL PROTECTED]> wrote: > > Bill Moran wrote: > > > The system can not replace programs that are in use, > > > > This is generally not the case. Unix lets you continue to access a file > > after > > it has been deleted, so long as the process hangs on to a file descriptor. > > This lets you replace programs in use, without running into the same > > problems > > that platforms like Windows have. > > What you say?: > > bash-2.05b$ su > Password: > bolivia# cp /usr/sbin/cron /home/wmoran/. > bolivia# cp /home/wmoran/cron /usr/sbin/. > cp: /usr/sbin/./cron: Text file busy > bolivia# mv /usr/sbin/cron /usr/sbin/cron- cp /blah/cron /usr/sbin/cron install does this behind the scenes. Warner ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Newbie Question About System Update
> Fact is, trying to update a running system could result in silent failures. > The system can not replace programs that are in use, so there's always the > chance that something or other won't get updated (cron would be an excellent > example ... do you always shut cron off when you update? How about syslogd?) Actually, it can. install goes to great lengths to make sure that it carefully moves the executable out of the way before replacing it. It won't go away until the last process to be executing out of it goes away. > That being said, I quite often do installworld on running systems because I > have no way to go to single-user mode. It almost always works well enough > for my purposes, but I don't want anyone to think that it's "OK" to do this, > as it's not guaranteed to work, and will most likely result in some programs > not being updated (such as the examples in the previous paragraphs). It usually works well enough most of the time. I do it all the time on my development machines. The problem is "well enough" and "most of the time." Warner ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Newbie Question About System Update
On Tuesday 19 April 2005 22:25, Karl Denninger wrote: > > > > My attitude is that if you don't boot -s, you are simply playing > > Russian-roulette with your system. Some day, it will bite you. > > > > Kent > > Not if your update procedure saves the old kernel. > > Yes, you will have to get there to recover. You have to get there (either > physically or serial console) anyway if it blows up on you. The only problem I can see with this is if one of the more exotic disk controller drivers or file systems drivers goes homicidal (diskicidal?). Booting multi, you will automount all your big disks and arrays giving the drivers the chance to wreak havoc before you can do much about it. This seems pretty unlikely on -STABLE though. You're still in trouble though because you've probably lost / which probably contains the backup of the old kernel. In conclusion, its probably best if disk controller drivers and filesystem drivers don't have bugs in them. Mark pgpnPo205kKDu.pgp Description: PGP signature
Re: Newbie Question About System Update
Hi, If you are working with a remote system, you should probably be using the "nextboot" utility for testing a new kernel after your "make buildworld", "make buildkernel" and "make installkernel". >From nextboot's man page : --- DESCRIPTION The nextboot utility allows specifying an alternate kernel and/or boot flags for the next time the machine is booted. Once the loader(8) loads in the new kernel information, it is deleted so in case the new kernel hangs the machine, once it is rebooted, the machine will automatically revert to its previous configuration. --- Just rename your new kernel and put back the backup as the default. You should probably also edit '/etc/rc.conf' to disable your services (except sshd of course! :D). Then, proceed with "nextboot -k $newkernelname". If everything works fine, you can set the new kernel as the default and finish your update with "mergemaster -p", "make installworld" and "mergemaster". If your are confident, you can reanable all your services in '/etc/rc.conf' and reboot one last time. Otherwise, you can test your services and reenable them one by one. WARNING: Bad things may and will probably happen if you forget to set your new kernel as the default after finishing your update. Your system might not come back online on your next reboot because you will have an old kernel with new system binaries. Have fun! -js - Original Message - From: "Kent Stewart" <[EMAIL PROTECTED]> To: Cc: "Dan Nelson" <[EMAIL PROTECTED]>; "Bill Moran" <[EMAIL PROTECTED]> Sent: Tuesday, April 19, 2005 5:02 PM Subject: Re: Newbie Question About System Update > On Tuesday 19 April 2005 01:39 pm, Dan Nelson wrote: > > You are forgetting that one of the real purposes of the boot -s is to > test your new kernel. If you have never been bitten by a kernel that > would only panic, you have no problems. If you have, you know that you > can boot the old kernel and continue without any problems until some > one solves the panic. You will not most likely hit that situation on a > security based version but this is freebsd-stable and it can happen at > any time. > > My attitude is that if you don't boot -s, you are simply playing > Russian-roulette with your system. Some day, it will bite you. > > Kent ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Newbie Question About System Update
On Tue, Apr 19, 2005 at 02:02:04PM -0700, Kent Stewart wrote: > On Tuesday 19 April 2005 01:39 pm, Dan Nelson wrote: > > In the last episode (Apr 19), Bill Moran said: > > > Chuck Swiger <[EMAIL PROTECTED]> wrote: > > > > Bill Moran wrote: > > > > > The system can not replace programs that are in use, > > > > > > > > This is generally not the case. Unix lets you continue to access > > > > a file after it has been deleted, so long as the process hangs on > > > > to a file descriptor. This lets you replace programs in use, > > > > without running into the same problems that platforms like > > > > Windows have. > > > > > > What you say?: > > > > > > bash-2.05b$ su > > > Password: > > > bolivia# cp /usr/sbin/cron /home/wmoran/. > > > bolivia# cp /home/wmoran/cron /usr/sbin/. > > > cp: /usr/sbin/./cron: Text file busy > > > bolivia# > > > > > > Notice that /usr/sbin/cron is in use (because my system is running > > > normally) I can copy _from_ that file, but I can not overwrite it. > > > > What you can do, however, is: create the new file under a temporary > > name, delete the original, and rename the temp file to the orignal's > > name, which is what /usr/bin/install does. I've done many > > installworlds on running systems without problems. > > You are forgetting that one of the real purposes of the boot -s is to > test your new kernel. If you have never been bitten by a kernel that > would only panic, you have no problems. If you have, you know that you > can boot the old kernel and continue without any problems until some > one solves the panic. You will not most likely hit that situation on a > security based version but this is freebsd-stable and it can happen at > any time. > > My attitude is that if you don't boot -s, you are simply playing > Russian-roulette with your system. Some day, it will bite you. > > Kent Not if your update procedure saves the old kernel. Yes, you will have to get there to recover. You have to get there (either physically or serial console) anyway if it blows up on you. The old kernel (and loadables for it) should ALWAYS be saved when updating "in place", lest you discover exactly what you're warning about the hard way. -- -- Karl Denninger ([EMAIL PROTECTED]) Internet Consultant & Kids Rights Activist http://www.denninger.netMy home on the net - links to everything I do! http://scubaforum.org Your UNCENSORED place to talk about DIVING! http://www.spamcuda.net SPAM FREE mailboxes - FREE FOR A LIMITED TIME! http://genesis3.blogspot.comMusings Of A Sentient Mind ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Bonnie++ finds nfs failure.
If I run "bonnie++ -s 4G -n 40" ... meaning create 4G files for the thruput test and create 40*1024 files for the random file test, it will die claiming the directory is not empty --- ie: deletion of some files failed. In this particular case, The server is an AMD64 5.4-STABLE and the client is AMD64 5.3-RELEASE-p5. The filesystem is a 1.0T RAID10 (geom) with softupdates enabled. Dave. -- |David Gilbert, Independent Contractor. | Two things can only be | |Mail: [EMAIL PROTECTED]| equal if and only if they | |http://daveg.ca | are precisely opposite. | =GLO ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Newbie Question About System Update
On Tuesday 19 April 2005 01:39 pm, Dan Nelson wrote: > In the last episode (Apr 19), Bill Moran said: > > Chuck Swiger <[EMAIL PROTECTED]> wrote: > > > Bill Moran wrote: > > > > The system can not replace programs that are in use, > > > > > > This is generally not the case. Unix lets you continue to access > > > a file after it has been deleted, so long as the process hangs on > > > to a file descriptor. This lets you replace programs in use, > > > without running into the same problems that platforms like > > > Windows have. > > > > What you say?: > > > > bash-2.05b$ su > > Password: > > bolivia# cp /usr/sbin/cron /home/wmoran/. > > bolivia# cp /home/wmoran/cron /usr/sbin/. > > cp: /usr/sbin/./cron: Text file busy > > bolivia# > > > > Notice that /usr/sbin/cron is in use (because my system is running > > normally) I can copy _from_ that file, but I can not overwrite it. > > What you can do, however, is: create the new file under a temporary > name, delete the original, and rename the temp file to the orignal's > name, which is what /usr/bin/install does. I've done many > installworlds on running systems without problems. You are forgetting that one of the real purposes of the boot -s is to test your new kernel. If you have never been bitten by a kernel that would only panic, you have no problems. If you have, you know that you can boot the old kernel and continue without any problems until some one solves the panic. You will not most likely hit that situation on a security based version but this is freebsd-stable and it can happen at any time. My attitude is that if you don't boot -s, you are simply playing Russian-roulette with your system. Some day, it will bite you. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Tuning for router performance
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] (Joe Greco) writes:
> No problems with high traffic rates. (For the purposes of this discussion,
> all traffic except ssh to the router is traffic /thru/ the router).
Yes sorry I should have also mentioned I was specifically using
64byte packets for PPS testing - not entirely real world traffic.
> I find this interesting, because the aggregate traffic through the router
> is clearly not anywhere near a gigabit. So it does appear that there is
> some sort of inadvertent cap on PPS here.
I think there always will be at some point, if only because the
hardware isn't not optimised for the task.
> 2) We need to remember that the design of the P4SC{8,i} is a bit crappy,
>in that the onboard ports consist of one CSA port (no problem here)
>and one PCI port - which Supermicro wisely placed on the 32-bit, 33 MHz
>legacy PCI bus. This could potentially limit the throughput on that
>port.
Not a problem for me as I'm only using the ethernet on that bus.
-Paul-
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Tuning for router performance
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] ("David Schwartz") writes:
>> I'm starting to hit errors at 150Kpps.
> I'm not sure why you're hitting errors at that speed. But here are
> a few suggestions:
Sorry - I left out a key piece of information, as I'm testing PPS
rather than throughput I'm using 64byte packets.
>> options HZ=1000 #for polling
> That's too low. 2000 is the minimum you should consider.
Thanks, I will try that and do some more testing.
> You probably want:
>
> kern.random.sys.harvest.ethernet=0
> kern.random.sys.hervest.interrupt=0
I tried these in my initial test, but they didn't seem to make any
difference for me. I'll try them in combination with the above.
> What are your current values for vm.kmem_size and vm.kmem_size_max?
vm.kmem_size: 335544320
vm.kmem_size_max: 335544320
-Paul-
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Newbie Question About System Update
On Tue, Apr 19, 2005 at 04:32:37PM -0400, Bill Moran wrote: > Chuck Swiger <[EMAIL PROTECTED]> wrote: > > Bill Moran wrote: > > > The system can not replace programs that are in use, > > > > This is generally not the case. Unix lets you continue to access a file > > after > > it has been deleted, so long as the process hangs on to a file descriptor. > > This lets you replace programs in use, without running into the same > > problems > > that platforms like Windows have. > > What you say?: > > bash-2.05b$ su > Password: > bolivia# cp /usr/sbin/cron /home/wmoran/. > bolivia# cp /home/wmoran/cron /usr/sbin/. > cp: /usr/sbin/./cron: Text file busy > bolivia# > > Notice that /usr/sbin/cron is in use (because my system is running > normally) I can copy _from_ that file, but I can not overwrite it. > > Apparenlty, nobody who is claiming this has _tried_ it. Try it yourself > and see. You can _not_ replace programs that have their Text section > in use (i.e. the code) because the demand pager has that area of the > file locked. You apparently cannot modify a program that is in use. What you *can* do is delete it and create a new file with the same name. Try using 'cp -f' instead of plain 'cp'. (Or use the install(1) utility, which is what installworld normally uses, which also unlinks the old file before creating the new.) -- Erik Trulsson [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: %idle stuck at 33%?
In article <[EMAIL PROTECTED]> you wrote: > > This kind of thing can happen if your world is out of sync with your > kernel. > > Kris > The world and kernel are in sync - I used a world/kernel build to generate the load (several times with the same source). I don't see the same behavior on a Dell desktop machine with 2 processors, hyperthreading disabled, so it must be something specific to the Dell 2650. - Mike H. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Newbie Question About System Update
In the last episode (Apr 19), Bill Moran said: > Chuck Swiger <[EMAIL PROTECTED]> wrote: > > Bill Moran wrote: > > > The system can not replace programs that are in use, > > This is generally not the case. Unix lets you continue to access a > > file after it has been deleted, so long as the process hangs on to > > a file descriptor. This lets you replace programs in use, without > > running into the same problems that platforms like Windows have. > > What you say?: > > bash-2.05b$ su > Password: > bolivia# cp /usr/sbin/cron /home/wmoran/. > bolivia# cp /home/wmoran/cron /usr/sbin/. > cp: /usr/sbin/./cron: Text file busy > bolivia# > > Notice that /usr/sbin/cron is in use (because my system is running > normally) I can copy _from_ that file, but I can not overwrite it. What you can do, however, is: create the new file under a temporary name, delete the original, and rename the temp file to the orignal's name, which is what /usr/bin/install does. I've done many installworlds on running systems without problems. -- Dan Nelson [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Newbie Question About System Update
Chuck Swiger <[EMAIL PROTECTED]> wrote: > Bill Moran wrote: > > The system can not replace programs that are in use, > > This is generally not the case. Unix lets you continue to access a file > after > it has been deleted, so long as the process hangs on to a file descriptor. > This lets you replace programs in use, without running into the same problems > that platforms like Windows have. What you say?: bash-2.05b$ su Password: bolivia# cp /usr/sbin/cron /home/wmoran/. bolivia# cp /home/wmoran/cron /usr/sbin/. cp: /usr/sbin/./cron: Text file busy bolivia# Notice that /usr/sbin/cron is in use (because my system is running normally) I can copy _from_ that file, but I can not overwrite it. Apparenlty, nobody who is claiming this has _tried_ it. Try it yourself and see. You can _not_ replace programs that have their Text section in use (i.e. the code) because the demand pager has that area of the file locked. -- Bill Moran Potential Technologies http://www.potentialtech.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: PXEBOOT/TFTPBOOT + big MD_ROOT problem
> Objet : Re: PXEBOOT/TFTPBOOT + big MD_ROOT problem > > Marc Olzheim wrote: > > >On Tue, Apr 19, 2005 at 09:52:07AM +0200, Emmanuel Chriqui wrote: > > > > > >>Hi, > >> > >>I'm trying to make very big MD_ROOT (300MB) sent using PXEBOOT+TFTPBOOT. > No > >>NFS. > >> > >> > > > >Any reasons for not using NFS ? > > > > > > > >>I use i386/5.4RC2/TFTPD/PXEBOOT+TFTPBOOT . > >>(same pb with a 5.3). > >> > >>Am I missing something obvious? > >> > >> > > > >I'm not sure. tftp itself is able to handle 32MB+ files, but maybe the > >loader isn't. > > > >A workaround, no using NFS, could be to tftp a second filesystem image > >on boot and mount that from the root filesystem. > > > >Marc > > > > > I assume that the PXE clients are diskless clients. If so, do they have > enough memory to handle this extremely large image? As for tfpt, it uses YES, diskless. And enough memory. > UDP. UDP is usually used for transfer small datagrams, for instance DNS > replies. It is also said to be an unreliable protocol. The client should > repeat the request when no data receives. I doubt this solution is You're right. However, pros : over 2 years this solution has proven to work *perfectly* for us, Reboots are rare and done using pools (~10 servers each time), NFS was horrible to handle and we lost data everytime traffic was intense. Cons : this was over linux. I believe NFS over FreeBSD works better (by I still have my linux servers... and they work great so..). > reliable and flexible enough. My idea for a workaround is creating a > ramdisk from a small boot image, and transfer the less necessary > userland binaries from the boot server to the ramdisk using normal ftp > connection. Yes. Thx. Emmanuel. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Newbie Question About System Update
On Tue, Apr 19, 2005 at 04:05:10PM -0400, Scott Robbins wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Tue, Apr 19, 2005 at 09:36:57PM +0200, K?vesd?n G?bor wrote: > > > > >This is generally not the case. Unix lets you continue to access a > > >file after it has been deleted, so long as the process hangs on to a > > >file descriptor. This lets you replace programs in use, without > > >running into the same problems that platforms like Windows have. > > > > Though this is true, I discourage You to upgrade a running system. I > > tried to upgarde 5.3-RELEASE to 5-STABLE without booting to single user > > mode. I simply sent a TERM signal to most of the processes, and tried to > > make installworld. There was some error messages, the system crashed and > > didn't boot anymore... > > There are a couple of servers that I have to upgrade remotely when > necessary. They are active during the working day and almost unused at > night--I just make sure the users know to not leave any files (two are > samba servers as well as doing other things) open if I'm planning an > upgrade--I'm fortunate that my users work with me, and there are only > two who have to be reminded, and neither gives me an argument about it. > > I'm never happy about doing it that way, but what I do is after the > reboot, shut down the various daemons and do the install world and > mergemaster. (This is only after testing the builds on a sacrificial > workstation). > > (And of course the obvious--DO NOT shut down the sshd daemon.) :) > > Ok, everyone who has NEVER ever made that mistake (or locked themself > out with a firewall rule, accidentally putting it into effect before > testing) raise their hand. :) > > > - -- > > Scott > > GPG KeyID EB3467D6 > ( 1B848 077D 66F6 9DB0 FDC2 A409 FA54 D575 EB34 67D6) > gpg --keyserver pgp.mit.edu --recv-keys EB3467D6 When I ran my ISP I updated FreeBSD "hot" all the time. I would build and verify on a "sandbox", and had a piece of custom software (two pieces, actually, a "sender" and "receiver") that would do the moral equivalent of an "rcp" but with moving and then unlinking each executable as it ran (looked at the "x" flag to see if something was executable), adjusting permissions after each file was moved. It was smart enough not to tamper with itself, of course :-> Then the cluster control daemon was told to reboot and off she went. Never got burned doing this; I used to update a cluster consisting of a LOT of machines - we had a window scheduled for it, so customers were warned, but in general due to the way the clustering software worked you'd be lucky if you even noticed unless you were logged into a shell account (at which point you'd lose the telnet session and have to sign back in) The "rolling update" was completely transparent to our web hosting customers (their processes would be assigned to a different machine before each was copied to the new code) It worked fabulously. I've still got the code around somewhere, and I can't imagine why it wouldn't work on the 5.x branch - there's nothing magical that's changed enough to cause trouble with it that I can see. -- -- Karl Denninger ([EMAIL PROTECTED]) Internet Consultant & Kids Rights Activist http://www.denninger.netMy home on the net - links to everything I do! http://scubaforum.org Your UNCENSORED place to talk about DIVING! http://www.spamcuda.net SPAM FREE mailboxes - FREE FOR A LIMITED TIME! http://genesis3.blogspot.comMusings Of A Sentient Mind ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Newbie Question About System Update
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, Apr 19, 2005 at 09:36:57PM +0200, K?vesd?n G?bor wrote: > > >This is generally not the case. Unix lets you continue to access a > >file after it has been deleted, so long as the process hangs on to a > >file descriptor. This lets you replace programs in use, without > >running into the same problems that platforms like Windows have. > > Though this is true, I discourage You to upgrade a running system. I > tried to upgarde 5.3-RELEASE to 5-STABLE without booting to single user > mode. I simply sent a TERM signal to most of the processes, and tried to > make installworld. There was some error messages, the system crashed and > didn't boot anymore... There are a couple of servers that I have to upgrade remotely when necessary. They are active during the working day and almost unused at night--I just make sure the users know to not leave any files (two are samba servers as well as doing other things) open if I'm planning an upgrade--I'm fortunate that my users work with me, and there are only two who have to be reminded, and neither gives me an argument about it. I'm never happy about doing it that way, but what I do is after the reboot, shut down the various daemons and do the install world and mergemaster. (This is only after testing the builds on a sacrificial workstation). (And of course the obvious--DO NOT shut down the sshd daemon.) :) Ok, everyone who has NEVER ever made that mistake (or locked themself out with a firewall rule, accidentally putting it into effect before testing) raise their hand. :) - -- Scott GPG KeyID EB3467D6 ( 1B848 077D 66F6 9DB0 FDC2 A409 FA54 D575 EB34 67D6) gpg --keyserver pgp.mit.edu --recv-keys EB3467D6 Buffy: I'm gonna give you all a nice, fun, normal evening if I have to kill every person on the face of the Earth to do it. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCZWR2+lTVdes0Z9YRApEVAJ4yccCFO7ThWLaJsM52mbP0aQkMAQCgsXfn eDogdcBoD5jpMJe8CO8xiWg= =IyKf -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ACPI suspend/resume
On Tue, 19.04.2005 at 17:58:59 +0300, Alexandru Balan wrote: > Hello list, > I have FreeBSD 5.4-STABLE on a Dell Latitude D505 > My main problem is that acpiconf -s 3 reobots the machine and -s 1 keeps > it going only for a few hours, draining the battery. Has anyone found > any workaround for this ? I've seen the problem presented on several > mailing lists but couldn't find a proper resolution This is a known problem pertaining nearly all Dell Laptops. Nate Lawson ([EMAIL PROTECTED]) probably knows *why* it's broken, but not how to fix it. I think he could fix it fairly fast, iff he got access to actual Dell hardware. Anyone? Ulrich Spörlein -- PGP Key ID: F0DB9F44 Encrypted mail welcome! Fingerprint: F1CE D062 0CA9 ADE3 349B 2FE8 980A C6B5 F0DB 9F44 Ok, which part of "Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn." didn't you understand? pgpgLXBTeFBVp.pgp Description: PGP signature
RE: PXEBOOT/TFTPBOOT + big MD_ROOT problem
> Objet : Re: PXEBOOT/TFTPBOOT + big MD_ROOT problem > > On Tue, Apr 19, 2005 at 09:31:10PM +0200, Emmanuel Chriqui wrote: > > This is roughly how it works under our linux servers, webservers, etc... > I > > was hoping to avoid that approach (less work.. less maintenance..). > > > > Am I the only one on earth to need a big MFSROOT ??? > > :) > > Hmm, I guess so. :-P > > Anyway, you might try > > http://pigseye.kennesaw.edu/~dyeske/freebsd/article.html Thx ! > ... > > Another idea is to use NFS just to use the loader to 'load -t mfs_root' > the mfsroot image. After that, you wouldn't depend on NFS anymore. > > Marc Very good idea. If my problem is related to TFTP + mfs_root than than this might work. Emmanuel. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: PXEBOOT/TFTPBOOT + big MD_ROOT problem
On Tue, Apr 19, 2005 at 09:31:10PM +0200, Emmanuel Chriqui wrote: > This is roughly how it works under our linux servers, webservers, etc... I > was hoping to avoid that approach (less work.. less maintenance..). > > Am I the only one on earth to need a big MFSROOT ??? > :) Hmm, I guess so. :-P Anyway, you might try http://pigseye.kennesaw.edu/~dyeske/freebsd/article.html Although I'm not sure the linker will allow you to link such a huge object into the kernel... I've used this patch on my netbooted FreeBSD 4.x servers, but never larger tham 10 MB. Another idea is to use NFS just to use the loader to 'load -t mfs_root' the mfsroot image. After that, you wouldn't depend on NFS anymore. Marc pgpcxPtjHJEO0.pgp Description: PGP signature
Re: Newbie Question About System Update
This is generally not the case. Unix lets you continue to access a file after it has been deleted, so long as the process hangs on to a file descriptor. This lets you replace programs in use, without running into the same problems that platforms like Windows have. Though this is true, I discourage You to upgrade a running system. I tried to upgarde 5.3-RELEASE to 5-STABLE without booting to single user mode. I simply sent a TERM signal to most of the processes, and tried to make installworld. There was some error messages, the system crashed and didn't boot anymore... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: PXEBOOT/TFTPBOOT + big MD_ROOT problem
> -Message d'origine- > De : [EMAIL PROTECTED] [mailto:owner-freebsd- > [EMAIL PROTECTED] De la part de Marc Olzheim > Envoyé : mardi 19 avril 2005 21:06 > À : Emmanuel Chriqui > Cc : freebsd-hackers@freebsd.org; freebsd-stable@freebsd.org > Objet : Re: PXEBOOT/TFTPBOOT + big MD_ROOT problem > > On Tue, Apr 19, 2005 at 09:52:07AM +0200, Emmanuel Chriqui wrote: > > Hi, > > > > I'm trying to make very big MD_ROOT (300MB) sent using PXEBOOT+TFTPBOOT. > No > > NFS. > > Any reasons for not using NFS ? Yes. Mainly : similar system already working great under linux for two years, NFS heavy traffic problems making data loss so difficult to solve (at least under Linux), cheap memory, better server independence when he got his system (tftp server shut down after the client servers got theirs images). > > > I use i386/5.4RC2/TFTPD/PXEBOOT+TFTPBOOT . > > (same pb with a 5.3). > > > > Am I missing something obvious? > > I'm not sure. tftp itself is able to handle 32MB+ files, but maybe the > loader isn't. TFTP linux->FreeBSD, FreeBsd->FreeBSD, FreeBSD->Linux ok for 500MB, 1GB, 1,5GB, works ok (well... at least on our servers..). > > A workaround, no using NFS, could be to tftp a second filesystem image > on boot and mount that from the root filesyste This is roughly how it works under our linux servers, webservers, etc... I was hoping to avoid that approach (less work.. less maintenance..). Am I the only one on earth to need a big MFSROOT ??? :) Emmanuel. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
matrox parhelia and hauppauge pvr350 questions
Hi, I would like to migrate my main workstation from windowsxp to freebsd 5.4-stable (I run a few free- and openbsd machines on a few servers and a laptop) I use a matrox parhelia 128mb (dual DVI) agp card which is connected to 2 LCD screens. I also run a Hauppauge PVR350 TV card to watch TV on my PC. I've a few questions: 1) Does someone run a matrox parhelia in Xorg 6.8.2 with freebsd5.x, what's your comment on it? 2) Is multi-screen (Xinerama) working with this card? 3) Is someone using hauppauge pvr350 TV card to watch tv in freebsd? 4) Is tv watching with the pvr somewhat user-friendly? Many many thanks for taking the time to respond Didier ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: PXEBOOT/TFTPBOOT + big MD_ROOT problem
Marc Olzheim wrote: On Tue, Apr 19, 2005 at 09:52:07AM +0200, Emmanuel Chriqui wrote: Hi, I'm trying to make very big MD_ROOT (300MB) sent using PXEBOOT+TFTPBOOT. No NFS. Any reasons for not using NFS ? I use i386/5.4RC2/TFTPD/PXEBOOT+TFTPBOOT . (same pb with a 5.3). Am I missing something obvious? I'm not sure. tftp itself is able to handle 32MB+ files, but maybe the loader isn't. A workaround, no using NFS, could be to tftp a second filesystem image on boot and mount that from the root filesystem. Marc I assume that the PXE clients are diskless clients. If so, do they have enough memory to handle this extremely large image? As for tfpt, it uses UDP. UDP is usually used for transfer small datagrams, for instance DNS replies. It is also said to be an unreliable protocol. The client should repeat the request when no data receives. I doubt this solution is reliable and flexible enough. My idea for a workaround is creating a ramdisk from a small boot image, and transfer the less necessary userland binaries from the boot server to the ramdisk using normal ftp connection. Cheers, Gábor Kövesdán ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Newbie Question About System Update
Bill Moran wrote: Matthias Buelow <[EMAIL PROTECTED]> wrote: [ ... ] Fact is, trying to update a running system could result in silent failures. True. It's better to shut down as many tasks as possible. The system can not replace programs that are in use, This is generally not the case. Unix lets you continue to access a file after it has been deleted, so long as the process hangs on to a file descriptor. This lets you replace programs in use, without running into the same problems that platforms like Windows have. -- -Chuck ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: PXEBOOT/TFTPBOOT + big MD_ROOT problem
On Tue, Apr 19, 2005 at 09:52:07AM +0200, Emmanuel Chriqui wrote: > Hi, > > I'm trying to make very big MD_ROOT (300MB) sent using PXEBOOT+TFTPBOOT. No > NFS. Any reasons for not using NFS ? > I use i386/5.4RC2/TFTPD/PXEBOOT+TFTPBOOT . > (same pb with a 5.3). > > Am I missing something obvious? I'm not sure. tftp itself is able to handle 32MB+ files, but maybe the loader isn't. A workaround, no using NFS, could be to tftp a second filesystem image on boot and mount that from the root filesystem. Marc pgpPpcYFwJ4OZ.pgp Description: PGP signature
Re: Please Suport Starsky2 DVB-S card please
Hi! On Tue, Apr 19, 2005 at 07:56:37PM +0200, Julian H. Stacey wrote: > > Hello there I would like to ask you if you could add to the final > > realase drivers for the SkyStar2 PCI card it is a Digital Sat-Reciver > > made by TechniSat Company, the bad thing though is that they do not > > suport it > > > > Thank you very much... > > http://www.freebsd.org/donations/index.html#components > > If donate & send one to developers, (perhaps sharing purchase cost > with another owner) & if you get tech. docs from manufacturer, your > chances of getting a developer to donate his time free may likely > rise dramaticaly. (No I'm Not looking for a card myself :-) There is something for SkyStar2 here: http://paradox.org.ua/ But it is "demo" version (haven't tried it myself) and there are not sources. /fjoe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD and NMAP
Thus spake Dominic Marks ([EMAIL PROTECTED]) [19/04/05 07:18]: : On Tuesday 19 April 2005 12:11, pck wrote: : > Hi, : > : > How can i hide from nmap that my OS is FreeBSD? Is this possible? : : # sysctl -ad | grep random_id : net.inet.ip.random_id: Assign random ip_id values : # echo 'net.inet.ip.random_id=1' >> /etc/sysctl.conf That doesn't hide the OS. That just makes the IP ID field random. One way to help: echo "net.inet.tcp.drop_synfin=1' >> /etc/sysctl.conf (Note that you need the "options TCP_DROP SYNFIN" line in your kernel config.) Other than that... randomize the packet fingerprint data. I know there's been at least one daemon that did this on Linux, as well as a kernel patch that did the same. But I'd ask: why? You're doing a significant amount of work for very little in return. - Damian ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Please Suport Starsky2 DVB-S card please
Maher Mohamed wrote: > Hello there I would like to ask you if you could add to the final > realase drivers for the SkyStar2 PCI card it is a Digital Sat-Reciver > made by TechniSat Company, the bad thing though is that they do not > suport it > > Thank you very much... http://www.freebsd.org/donations/index.html#components If donate & send one to developers, (perhaps sharing purchase cost with another owner) & if you get tech. docs from manufacturer, your chances of getting a developer to donate his time free may likely rise dramaticaly. (No I'm Not looking for a card myself :-) - Julian StaceyNet & Sys Eng Consultant, Munich http://berklix.com Mail in Ascii (Html=Spam). Ihr Rauch = mein allergischer Kopfschmerz. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Newbie Question About System Update
> Date: Tue, 19 Apr 2005 09:28:39 -0400 > From: Bill Moran <[EMAIL PROTECTED]> > Sender: [EMAIL PROTECTED] > > Jim Campbell <[EMAIL PROTECTED]> wrote: > > > I've been away from *NIX a few years. I have been playing with FreeBSD > > for a week or so now with mixed results. I am using release 4.11 > > because for some reason 5.3 has problems seeing my hard drives. 4.11, > > Red Hat Linux and NetBSD have no such trouble. > > > > This afternoon I used the "Updating Sources with CVSup" in the FreeBSD > > Cheat Sheets and everything worked as advertized. I believe that it > > advised against using "make world" and suggested that I use "19.4.1 The > > Canonical Way to Update Your System" in the Handbook. I went through > > the following steps with no problem: > > > > # make buildworld > > # make installworld > > # mergemaster > > # reboot > > This is not correct, and this is not what 19.4.1 says. The correct > procedure is as Mike Schultz described. Please review that section of > the handbook. > > If you did, indeed, do as you described, then you have a world that's > out of sync with your kernel. Try this: > 1) Boot in to single user mode > 2) fsck > 3) mount -a > 4) cd /usr/src > 5) make buildkernel > 6) make installkernel > 7) reboot > > If you're unable to complete those steps, then you may be better off > reinstalling and trying again - write it off as part of the learning > process. There are ways to restore your system if you've made this > mistake and the above doesn't work, but it's rather advanced stuff. The right answer is to read and follow the instructions in /usr/src/UPDATING. (They are near the bottom of the file.) The list above missed adjkerntz (not needed if the hardware clock is running UTC). Adding swapon -a is a good safety net, too. I was recently bitten when I forgot. But rather then generate more poor or incomplete examples for people to trip over, the canonical answer should be to follow the instructions in UPDATING. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Newbie Question About System Update
Matthias Buelow <[EMAIL PROTECTED]> wrote: > Jim Campbell <[EMAIL PROTECTED]> writes: > > >After that, I ran into problems. It took me a little while to figure > >out how to do "boot -s". However, it appears that a lot of the > >directories aren't mounted and the next scripts aren't in the path. For > >example, I can't figure out how to do the "mergemaster -p". > > You don't have to do it in single user mode, I never did. I don't know > why it is recommended that one boots in single user in the Makefile, > perhaps to get a quiescent system without any users and services that > would interfere. But that can also be achieved by stopping the > high-volume services on the machine after booting, and on a personal > machine (workstation PC) it doesn't matter anyways. Often it's not even > possible to boot into single-user, for example if you don't have > physical control over the machine (like in a co-lo situation). This isn't really true. Fact is, trying to update a running system could result in silent failures. The system can not replace programs that are in use, so there's always the chance that something or other won't get updated (cron would be an excellent example ... do you always shut cron off when you update? How about syslogd?) That being said, I quite often do installworld on running systems because I have no way to go to single-user mode. It almost always works well enough for my purposes, but I don't want anyone to think that it's "OK" to do this, as it's not guaranteed to work, and will most likely result in some programs not being updated (such as the examples in the previous paragraphs). On a production system, you should have a serial terminal connected so you can go to single-user mode remotely to do updates. There are fairly inexpensive serial terminal boxes available from a number of vendors, and if you have a spare machine available, you can always hook it up as a serial terminal. -- Bill Moran Potential Technologies http://www.potentialtech.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: no dump, not enough free space on device
>> stable of march 7, but this has been a long-term problem on >> this system >> >> system has 1g of real memory >> >> real memory = 1073217536 (1023 MB) >> avail memory = 1044914176 (996 MB) >> >> 2g of swap >> >> # swapinfo >> Device 1024-blocks UsedAvail Capacity >> /dev/twed0s1b 2097152 1428 2095724 0% >> >> has it set up to save disk flowers >> >> dumpdev="/dev/twed0s1b" # Device name to crashdump to (or NO). >> dumpdir="/var/crash"# Directory where crash dumps are to be stored > > How about free space on /var/crash? ! thank you! randy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: no dump, not enough free space on device
Citerar Randy Bush <[EMAIL PROTECTED]>: stable of march 7, but this has been a long-term problem on this system system has 1g of real memory real memory = 1073217536 (1023 MB) avail memory = 1044914176 (996 MB) 2g of swap # swapinfo Device 1024-blocks UsedAvail Capacity /dev/twed0s1b 2097152 1428 2095724 0% has it set up to save disk flowers dumpdev="/dev/twed0s1b" # Device name to crashdump to (or NO). dumpdir="/var/crash"# Directory where crash dumps are to be stored How about free space on /var/crash? /thn -- --- Svensk Aktuell Elektronik AB Thomas Nyström Box 10Phone: +46 8 35 92 85 S-191 21 SollentunaFax: +46 8 35 92 86 Sweden Email: [EMAIL PROTECTED] --- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
no dump, not enough free space on device
stable of march 7, but this has been a long-term problem on this system system has 1g of real memory real memory = 1073217536 (1023 MB) avail memory = 1044914176 (996 MB) 2g of swap # swapinfo Device 1024-blocks UsedAvail Capacity /dev/twed0s1b 2097152 1428 2095724 0% has it set up to save disk flowers dumpdev="/dev/twed0s1b" # Device name to crashdump to (or NO). dumpdir="/var/crash"# Directory where crash dumps are to be stored but savecore: reboot after panic: ffs_blkfree: freeing free block savecore: no dump, not enough free space on device (663614 available, need 1048066) savecore: unsaved dumps found but not saved randy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ACPI suspend/resume
Hello list, I have FreeBSD 5.4-STABLE on a Dell Latitude D505 My main problem is that acpiconf -s 3 reobots the machine and -s 1 keeps it going only for a few hours, draining the battery. Has anyone found any workaround for this ? I've seen the problem presented on several mailing lists but couldn't find a proper resolution Thanks -- Alex signature.asc Description: This is a digitally signed message part -- This message was scanned for spam and viruses by BitDefender. For more information please visit http://linux.bitdefender.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Please Suport Starsky2 DVB-S card please
Hello there I would like to ask you if you could add to the final realase drivers for the SkyStar2 PCI card it is a Digital Sat-Reciver made by TechniSat Company, the bad thing though is that they do not suport it Thank you very much... Mohamed M. Maher ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: NFS defaults for read/write blocksize....(Was: Re: 5.4/amd64 console hang)
On Mon, Apr 18, 2005 at 10:43:46AM +0200, Claus Guttesen wrote: > > Has it even been considered to up these values to something bigger?? > > Read- and write-size of 32768 seems to work optimal for me: > > nfssrv:/nfsmnt /localsrv/nfsmnt nfs > rw,tcp,intr,nfsv3,-w=32768,-r=32768 00 I use the same, but then also a ,-a=4 to set the read ahead to maximum on remote systems. Marc pgp088p5Csh1l.pgp Description: PGP signature
Re: Newbie Question About System Update
Jim Campbell <[EMAIL PROTECTED]> wrote: > I've been away from *NIX a few years. I have been playing with FreeBSD > for a week or so now with mixed results. I am using release 4.11 > because for some reason 5.3 has problems seeing my hard drives. 4.11, > Red Hat Linux and NetBSD have no such trouble. > > This afternoon I used the "Updating Sources with CVSup" in the FreeBSD > Cheat Sheets and everything worked as advertized. I believe that it > advised against using "make world" and suggested that I use "19.4.1 The > Canonical Way to Update Your System" in the Handbook. I went through > the following steps with no problem: > > # make buildworld > # make installworld > # mergemaster > # reboot This is not correct, and this is not what 19.4.1 says. The correct procedure is as Mike Schultz described. Please review that section of the handbook. If you did, indeed, do as you described, then you have a world that's out of sync with your kernel. Try this: 1) Boot in to single user mode 2) fsck 3) mount -a 4) cd /usr/src 5) make buildkernel 6) make installkernel 7) reboot If you're unable to complete those steps, then you may be better off reinstalling and trying again - write it off as part of the learning process. There are ways to restore your system if you've made this mistake and the above doesn't work, but it's rather advanced stuff. -- Bill Moran Potential Technologies http://www.potentialtech.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Newbie Question About System Update
Jim Campbell <[EMAIL PROTECTED]> writes: >After that, I ran into problems. It took me a little while to figure >out how to do "boot -s". However, it appears that a lot of the >directories aren't mounted and the next scripts aren't in the path. For >example, I can't figure out how to do the "mergemaster -p". You don't have to do it in single user mode, I never did. I don't know why it is recommended that one boots in single user in the Makefile, perhaps to get a quiescent system without any users and services that would interfere. But that can also be achieved by stopping the high-volume services on the machine after booting, and on a personal machine (workstation PC) it doesn't matter anyways. Often it's not even possible to boot into single-user, for example if you don't have physical control over the machine (like in a co-lo situation). mkb. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [PATCH] Re: /etc/rc.d/sshd : "kldload random" missing?
On Tue, 19 Apr 2005 17:48, Rob wrote: > My earlier patch to the rc.d/sshd script was for > loading the 'random.ko' module, if needed. But the > random script does not do that. > > Should then the random script be extended by also > checking whether loading 'random.ko' needs to be > done? I think so. Try it and see 8-) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgpbvds3He99L.pgp Description: PGP signature
Re: some simple nfs-benchmarks on 5.4 RC2
> When you say 'ide->fiber' that could mean a lot of things. Is this a single > drive, or a RAID subsystem? Yes, I do read it different now ;-) It's a raid 5 with 12 400 GB drives split into two volumes (where I performed the test on one of them). regards Claus ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD and NMAP
On Tue, 19 Apr 2005, peceka wrote: >> > How can i hide from nmap that my OS is FreeBSD? Is this possible? >> >> # sysctl -ad | grep random_id >> net.inet.ip.random_id: Assign random ip_id values >> # echo 'net.inet.ip.random_id=1' >> /etc/sysctl.conf > >After that: >Interesting ports on 192.168.1.248: >(The 1643 ports scanned but not shown below are in state: closed) >Port State Service >22/tcp openssh >Device type: general purpose >Running (JUST GUESSING) : FreeBSD 5.X|4.X (95%), Apple Mac OS X 10.1.X >(88%), OpenBSD 3.X|2.X (88%), Apple Mac OS 8.X (85%) >Aggressive OS guesses: FreeBSD 5.0-RELEASE (95%), Apple Mac OS X >10.1.5 (88%), FreeBSD 4.3 - 4.4PRERELEASE (88%), FreeBSD 5.0-RELEASE >(x86) (88%), FreeBSD 5.1-CURRENT (June 2003) on Sparc64 (88%), OpenBSD >3.0 or 3.3 (88%), Apple Mac OS X 10.1.4 (Darwin Kernel 5.4) on iMac >(86%), FreeBSD 4.5-RELEASE (or -STABLE) through 4.6-RC (X86) (86%), >FreeBSD 4.7-RELEASE (86%), FreeBSD 5.0-RELEASE or -CURRENT (Jan 2003) >(86%) >No exact OS matches for host (test conditions non-ideal). >Uptime 0.003 days (since Tue Apr 19 13:22:41 2005) > >So it didn't help much... > So, try this: block in log quick proto tcp flags FUP/WEUAPRSF block in log quick proto tcp flags WEUAPRSF/WEUAPRSF block in log quick proto tcp flags SRAFU/WEUAPRSF block in log quick proto tcp flags /WEUAPRSF block in log quick proto tcp flags SR/SR block in log quick proto tcp flags SF/SF (in pf.conf) -- Michał 'max' Marciniak felix.fizyka.amu.edu.pl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: some simple nfs-benchmarks on 5.4 RC2
Claus Guttesen wrote: Q: Will I get better performance upgrading the server from dual PIII to dual Xeon? A: rsync is CPU intensive, so depending on how much cpu you were using for this, you may or may not gain. How busy was the server during that time? Is this to a single IDE disk? If so, you are probably bottlenecked by that IDE drive. The storage is ide->fiber. Using tcp-mounts and peaking 100 MB/s it used just about 100 % cpu. Rsync was only used to copy the folder recursively (-a), it used nfs to trasnfer the files to the nfs-server. When you say 'ide->fiber' that could mean a lot of things. Is this a single drive, or a RAID subsystem? Eric -- Eric AndersonSr. Systems AdministratorCentaur Technology A lost ounce of gold may be found, a lost moment of time never. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: some simple nfs-benchmarks on 5.4 RC2
> > Q: > > Will I get better performance upgrading the server from dual PIII to dual > > Xeon? > > A: > > rsync is CPU intensive, so depending on how much cpu you were using for this, > you may or may not gain. How busy was the server during that time? Is this > to > a single IDE disk? If so, you are probably bottlenecked by that IDE drive. The storage is ide->fiber. Using tcp-mounts and peaking 100 MB/s it used just about 100 % cpu. Rsync was only used to copy the folder recursively (-a), it used nfs to trasnfer the files to the nfs-server. regards Claus ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD and NMAP
On 4/19/05, Dominic Marks <[EMAIL PROTECTED]> wrote: > On Tuesday 19 April 2005 12:11, pck wrote: > > Hi, > > > > How can i hide from nmap that my OS is FreeBSD? Is this possible? > > # sysctl -ad | grep random_id > net.inet.ip.random_id: Assign random ip_id values > # echo 'net.inet.ip.random_id=1' >> /etc/sysctl.conf After that: Interesting ports on 192.168.1.248: (The 1643 ports scanned but not shown below are in state: closed) Port State Service 22/tcp openssh Device type: general purpose Running (JUST GUESSING) : FreeBSD 5.X|4.X (95%), Apple Mac OS X 10.1.X (88%), OpenBSD 3.X|2.X (88%), Apple Mac OS 8.X (85%) Aggressive OS guesses: FreeBSD 5.0-RELEASE (95%), Apple Mac OS X 10.1.5 (88%), FreeBSD 4.3 - 4.4PRERELEASE (88%), FreeBSD 5.0-RELEASE (x86) (88%), FreeBSD 5.1-CURRENT (June 2003) on Sparc64 (88%), OpenBSD 3.0 or 3.3 (88%), Apple Mac OS X 10.1.4 (Darwin Kernel 5.4) on iMac (86%), FreeBSD 4.5-RELEASE (or -STABLE) through 4.6-RC (X86) (86%), FreeBSD 4.7-RELEASE (86%), FreeBSD 5.0-RELEASE or -CURRENT (Jan 2003) (86%) No exact OS matches for host (test conditions non-ideal). Uptime 0.003 days (since Tue Apr 19 13:22:41 2005) So it didn't help much... Best Regards, p. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: some simple nfs-benchmarks on 5.4 RC2
Claus Guttesen wrote: Hi. Sorry for x-posting but the thread was originally meant for freebsd-stable but then a performance-related question slowly emerged into the message ;-) Inspired by the nfs-benchmarks by Willem Jan Withagen I ran some simple benchmarks against a FreeBSD 5.4 RC2-server. My seven clients are RC1 and is a mix of i386 and amd64. The purpose of this test was *not* to measure throughput using various r/w-sizes. So all clients were mounted using r/w-sizes of 32768. The only difference was the usage of udp- or tcp-mounts. I only ran the test once. The server has net.isr.enable set to 1 (active), gbit-nic is em. Used 'systat -ifstat 1' to measure throughput. The storage is ide->fiber using a qlogic 2310 hba. It's a dual PIII at 1.3 GHz. I'm rsyncing to and from the nfsserver, the files are some KB (thumbnails) and and at most 1 MB (the image itself). The folder is approx. 1.8 GB. The mix of files very much reflects our load. *to* nfs-server *from* nfs-server tcp41 MB/s 100 MB/s udp 30 MB/s 74 MB/s In my environment tcp is (quite) faster than udp, so I'll stick to that in the near future. So eventhough I only made one run the tcp-times are so much faster and it utilized the cpu more that I beleive doing more runs would only level the score a bit. Q: Will I get better performance upgrading the server from dual PIII to dual Xeon? A: rsync is CPU intensive, so depending on how much cpu you were using for this, you may or may not gain. How busy was the server during that time? Is this to a single IDE disk? If so, you are probably bottlenecked by that IDE drive. Eric -- Eric AndersonSr. Systems AdministratorCentaur Technology A lost ounce of gold may be found, a lost moment of time never. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FreeBSD and ProPolice Smashing Stack Protector
Hi, does anybody use ProPolice Smashing Stack Protector for FreeBSD (http://www.research.ibm.com/trl/projects/security/ssp/buildfreebsd.html)? Is this stable with 5.4? If not what else can I use to improve security of my OS? Best Regards, p. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
some simple nfs-benchmarks on 5.4 RC2
Hi. Sorry for x-posting but the thread was originally meant for freebsd-stable but then a performance-related question slowly emerged into the message ;-) Inspired by the nfs-benchmarks by Willem Jan Withagen I ran some simple benchmarks against a FreeBSD 5.4 RC2-server. My seven clients are RC1 and is a mix of i386 and amd64. The purpose of this test was *not* to measure throughput using various r/w-sizes. So all clients were mounted using r/w-sizes of 32768. The only difference was the usage of udp- or tcp-mounts. I only ran the test once. The server has net.isr.enable set to 1 (active), gbit-nic is em. Used 'systat -ifstat 1' to measure throughput. The storage is ide->fiber using a qlogic 2310 hba. It's a dual PIII at 1.3 GHz. I'm rsyncing to and from the nfsserver, the files are some KB (thumbnails) and and at most 1 MB (the image itself). The folder is approx. 1.8 GB. The mix of files very much reflects our load. *to* nfs-server *from* nfs-server tcp41 MB/s 100 MB/s udp 30 MB/s 74 MB/s In my environment tcp is (quite) faster than udp, so I'll stick to that in the near future. So eventhough I only made one run the tcp-times are so much faster and it utilized the cpu more that I beleive doing more runs would only level the score a bit. Q: Will I get better performance upgrading the server from dual PIII to dual Xeon? A: regards Claus ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD and NMAP
On Tuesday 19 April 2005 12:11, pck wrote: > Hi, > > How can i hide from nmap that my OS is FreeBSD? Is this possible? # sysctl -ad | grep random_id net.inet.ip.random_id: Assign random ip_id values # echo 'net.inet.ip.random_id=1' >> /etc/sysctl.conf > > Best Regards, > p. > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- Dominic ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FreeBSD and NMAP
Hi, How can i hide from nmap that my OS is FreeBSD? Is this possible? Best Regards, p. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SuperMicro X5DP8-G2MB/(2)XEON 2.4/1GB RAM 5.4-S Freeze
On Tue, Apr 12, 2005 at 05:01:43PM +0200, Marc Olzheim wrote: > On Tue, Apr 12, 2005 at 10:40:10AM -0400, Don Bowman wrote: > > The problem is with the periodic SMM interrupt and the bios. > > > > The attached program (ich-periodic-smm-disable.c) will fix the problem. > > For more information on what it does, see the Intel ICH3 datasheet. > > > > compile as 'gcc ich-periodic-smm-disable.c; ./a.out' and you will be > > good. > > Run this on each boot. > > > > I think you only need to clear PERIODIC_EN. > > Ok, I'll try it right away, thanks a lot! This clearly solves it. The machines are now up for longer than a week for the first time since I booted FreeBSD 5.x on them. Thanks again! Marc pgpAN3SZtboNG.pgp Description: PGP signature
Re: [PATCH] Re: /etc/rc.d/sshd : "kldload random" missing?
--- Daniel O'Connor <[EMAIL PROTECTED]> wrote: > On Tue, 19 Apr 2005 17:06, Daniel O'Connor wrote: > > On Tue, 19 Apr 2005 16:43, Rob wrote: > > > Should I submit a patch here? > > > > > > Following patch works fine for me > > > (be aware some lines are wrapped :[ ) > > > > I think a more correct solution would be to make a > 'random' rc.d script > > which sshd depends on (and others if they're found > to need it) > > Heh actually now that I look.. there IS a random > script already.. > > Perhaps.. > [inchoate 17:08] /etc/rc.d >diff -u sshd.orig sshd > --- sshd.orig Tue Apr 19 17:07:52 2005 > +++ sshdTue Apr 19 17:07:59 2005 > @@ -5,7 +5,7 @@ > # > > # PROVIDE: sshd > -# REQUIRE: LOGIN cleanvar > +# REQUIRE: LOGIN cleanvar random > > . /etc/rc.subr My earlier patch to the rc.d/sshd script was for loading the 'random.ko' module, if needed. But the random script does not do that. Should then the random script be extended by also checking whether loading 'random.ko' needs to be done? Rob. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
PXEBOOT/TFTPBOOT + big MD_ROOT problem
Hi, I'm trying to make very big MD_ROOT (300MB) sent using PXEBOOT+TFTPBOOT. No NFS. It's a sort of diskless machine with all the system on ram. There is a problem when the preloaded image is >~32MB. Kernel loads but it does not seem to find the files. It seems as if only part of the image is really there. With a "small" image (<~32MB), no probleme. I use the same image, off course, same init etc... just more data for my application in the big image case. I use a classic mfs_root approche to make my image dd if=/dev/zero of=$MFS_FILE bs=1k count=$SIZE mdconfig -a -t vnode -f $MFS_FILE -u0 bsdlabel -w /dev/md0 newfs /dev/md0a mount /dev/md0a $MFS_FILE_MOUNT cp ... my content... umount $MFS_FILE_MOUNT fsck -t ufs /dev/md0a mdconfig -d -u 0 then I mount the $MFS_FILE_MOUNT . I use i386/5.4RC2/TFTPD/PXEBOOT+TFTPBOOT . (same pb with a 5.3). Am I missing something obvious? Emmanuel. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
4.x smbfs getdirentries() failure - need help debugging
Hi all, Have been doing my best to plod through debugging an issue with SMBFS on FreeBSD 4.11, where with a certain size directory, getdirentries() returns errno=9 (Bad file descriptor) when it reaches the end of the directory listing. I've traced it that far and found PR 78953 that appears to be the same issue, but am a bit out of my depth as to where to go from here. http://www.freebsd.org/cgi/query-pr.cgi?pr=78953 Would anyone be able to provide any pointers on where to go from here in trying to track down the cause? I've provided instructions that reliably allow me to reproduce the problem with a Windows XP machine as the source for the smbfs share, if anyone wants to have a look... At this point I'm guessing I need DDB to figure out what the kernel's doing and determine exactly where & why this error is arrising. Any help would be much appreciated, as at this point I'm into the unchartered (for me) world of the kernel! :-) Regards Antony ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [PATCH] Re: /etc/rc.d/sshd : "kldload random" missing?
On Tue, 19 Apr 2005 17:06, Daniel O'Connor wrote: > On Tue, 19 Apr 2005 16:43, Rob wrote: > > Should I submit a patch here? > > > > Following patch works fine for me > > (be aware some lines are wrapped :[ ) > > I think a more correct solution would be to make a 'random' rc.d script > which sshd depends on (and others if they're found to need it) Heh actually now that I look.. there IS a random script already.. Perhaps.. [inchoate 17:08] /etc/rc.d >diff -u sshd.orig sshd --- sshd.orig Tue Apr 19 17:07:52 2005 +++ sshdTue Apr 19 17:07:59 2005 @@ -5,7 +5,7 @@ # # PROVIDE: sshd -# REQUIRE: LOGIN cleanvar +# REQUIRE: LOGIN cleanvar random . /etc/rc.subr -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgppzbcp2gttG.pgp Description: PGP signature
Re: [PATCH] Re: /etc/rc.d/sshd : "kldload random" missing?
On Tue, 19 Apr 2005 16:43, Rob wrote: > Should I submit a patch here? > > Following patch works fine for me > (be aware some lines are wrapped :[ ) I think a more correct solution would be to make a 'random' rc.d script which sshd depends on (and others if they're found to need it) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgpgnU1qDfpNO.pgp Description: PGP signature
SIIG Multiport Card
Thanks to Peter Wemm for solving the final step in getting the SIIG 4-port card to work. You must reset its clock frequency back to a normal speed as follows: Edit /sys/dev/puc/pucdata.c Find the first instance of "Oxford Semiconductor OX16PCI954 UARTs". Change the four COM_FREQ entries to COM_FREQ * 10 Recompile. Watch all the ports magically begin to work. Kirk McKusick ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.4-RC2 kldload snd_driver crashes ums0
I also encountered this on a Thinkpad T42. My workaround was to load the sound module via /boot/loader.conf (i.e. snd_ich_load="YES"). -mark ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
[PATCH] Re: /etc/rc.d/sshd : "kldload random" missing?
--- Kris Kennaway <[EMAIL PROTECTED]> wrote:
> On Sun, Apr 17, 2005 at 08:48:37PM -0700, Rob wrote:
> >
> > Hi,
> >
> > I noticed that 'random.ko' module is required
> > by ssh, especially when running the server sshd.
> > However, the sshd script in /etc/rc.d does not
> > verify the pressence of the random.ko module and
> > neither loads it if necessary. Shouldn't that be
> > added?
> >
> > I bring this up, since I have observed that the
> > nfsserver.ko module is automagically loaded by the
> > /etc/rc.d/nfsserver script.
> >
> > Both cases seem to have some similarity.
>
> Sounds like a great opportunity to submit a patch!
> :)
Should I submit a patch here?
Following patch works fine for me
(be aware some lines are wrapped :[ )
--- /etc/rc.d/sshd Sun Oct 10 18:50:54 2004
+++ /etc/rc.d/sshd Tue Apr 19 15:56:12 2005
@@ -80,6 +80,14 @@
sshd_precmd()
{
+if ! ${SYSCTL} kern.random >/dev/null 2>&1;
then
+if ! kldload random; then
+warn 'Could not load random
module'
+return 1
+fi
+fi
+
if [ ! -f /etc/ssh/ssh_host_key -o \
! -f /etc/ssh/ssh_host_dsa_key -o \
! -f /etc/ssh/ssh_host_rsa_key ]; then
__
Do you Yahoo!?
Make Yahoo! your home page
http://www.yahoo.com/r/hs
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
