Trouble with 4.3-RELEASE compiler
Hi, I was installing a squid server with 4.3-RELEASE, and found that FreeBSD has now a bug in the compiler that affects squid. The default compilation of squid is with CFLAGS=-g -O2 -Wall, and this setup triggers the bug. I've left a trimmed down copy of the problem files at ftp://ftp.jonny.eng.br/hidden/jonny/trouble.tgz, compile it with gcc -g -O2 -Wall teste.c rfc1035.c, and see the bug happening. Remove the -O2 or change it for -O, and see it going away. Should this be a reason to roll back the compiler to version 2.95.2, as it was before Tue Apr 10 19:23:19 2001 UTC, when it changed to 2.95.3? What to do with the upcoming CDs? Jonny -- João Carlos Mendes Luís [EMAIL PROTECTED] Networking Engineer [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Seti project / stats reset, new version available
#define quoting(Stefan Bethke)
// Kris Kennaway wrote:
// > On Tue, 18 May 1999, Ueda, Kazukiyo wrote:
// > One thing I've been meaning to look at though is that it seems to run it
// > at niceness 1, which isn't exactly friendly to the other consumers of
// > CPU. You should be able to tweak it easily, though.
//
// Would you suggest a different default nice level, then, and what should it
// be?
//
// One can easily modifiy ${PREFIX}/etc/rc.d/setiathome.sh to run it with
// -nice 100, and I'm open to making a level other that 1 the default.
What about idprio ? And the installer or manual could also suggest
the sysctl tweaks to avoid lazy CPU response.
Jonny
--
João Carlos Mendes Luís jo...@jonny.eng.br
Networking Enginner j...@ieee.org
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
Re: Seti project / stats reset, new version available
#define quoting(Matthew Dillon) // This reduces the effect an idprio seti background task has on the rest of // the system. Yeah... I was going to ask just this. My users complained about server response after starting setiathome. // sysctl -w kern.quantum=2 Humm, my systems are configured with a value with 10: krakatoa::root [650] sysctl kern | grep quantum kern.quantum: 10 This both in 3.1-stable (Early May) and 2.2.8-stable (latest). Are you talking about a 4.0-current setup ? // The default is 100,000 ( 100ms ) which, for a modern cpu, is // much more chunky then it needs to be. Reducing it to 20ms // makes a big difference. At 10 I can feel the slow response // with seti running in the background. At 2 it is much less // pronounced. What are the drawbacks of this ? More CPU time spent in context switches ? Jonny -- João Carlos Mendes Luís jo...@jonny.eng.br Networking Enginner j...@ieee.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
