Hi,
On Fri, 24 Sep 1999, Mark Powell wrote:
> I have INN v2.2 running happily on a 3.1-STABLE machine, with all mmap
> options turned on. I read of mmap problems with 3.2-stable. Maybe my
> server just isn't loaded enough to grok on these problmes, but when I set
> up a new news server should I stay with 3.1 or have these problems been
> fixed in 3.3? Cheers.
You'd better stay with what it works for you right now. I'm sorry to say
it but since upgrading to 3.2-STABLE about end of August I get random
freezes every 1-2 days and even in 3.3-STABLE as of 20th September this
seems to not have been fixed; other people also reported on -stable
problems they had with 3.3 ...
Before any of you start flaming me about hardware problems let me assure
you I have thoroughly checked the machine and had DDB compiled in kernel;
I also might add that this machine had NO problems before upgrading to
3.2/3.3 and had respectable uptimes (now I can't get over 3 days of
uptime).
This is not intended to subminate FreeBSD's image but rather to launch a
"HEADS UP" warning in respect of -stable branch stability in this period
of time. I'm willing to cooperate with whoever wants to fix this in the
limits of my possibilities (this is a production server)...
PS: I could have filed a PR but I can't figure any way of reproducing
this -- just a double panic caught by my co-worker, details posted on
-stable on 19th Sep with "3.2-STABLE hangs after several hours" in
the subject...
Thank you,
Ady (@warpnet.ro)
Warp Net Technologies
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
