> At 04:28 PM 10/25/2001 +0000, paul@... wrote:
> >Chuck Esterbrook <ChuckEsterbrook@...> wrote:
> > >
> > >>I assume that 0.6 will:
> > >>----------------------------------
> > >>* fix the console hanging and socket binding problems that
> > >>Jeff's been working on
That fix is in the latest CVS already.
> > >Those are either op sys or Python problems; not Webware.=20
> I'm not aware of
> > >any outstanding work in this area other than providing=20
> convenient options
> > >for discarding daemon output.
I have a few lines of code in ThreadedAppServer that fix the problem by
changing stdout and stderr when in daemon mode so FreeBSD isn't a
problem anymore for me. Chuck said he'd add a config option to turn
this feature on.
If its not too late, the fix to socketmodule.c so SSL reads no longer
lock all threads will make it into Python 2.2. Since that was so easy
for them to fix, I posted the problem that linux and BSD behave
differently in regard to printing to closed consoles. Maybe they can
fix that too. Even if it's the OS and not Python's fault, maybe "print"
should swallow exceptions?
Regarding which OS to use, I wanted to use OpenBSD just from hearing
that "it's the most secure OS out of the box". I didn't want to spend
my days becoming a security expert. But at the time (only a few months
ago), OpenBSD did not support multiple processors and the box I was
going to use had two. I heard they were working on it, maybe they have
support for SMP now. So, I went with FreeBSD and have been really
pleased with it.