[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <5.2.1.1.2.20030428192136.00a8c830@molson.wixb.com>
Date: Mon, 28 Apr 2003 19:26:05 -0500
From: "J.D. Bronson" <jeff@...c.com>
To: popa3d-users@...ts.openwall.com
Subject: Re: popa3d on solaris 9
At 07:18 PM 04/28/2003, you wrote:
>On Mon, Apr 28, 2003 at 07:04:33PM -0500, J.D. Bronson wrote:
> > At 07:00 PM 04/28/2003, Solar Designer wrote:
> > >If you're really into performance, then Solaris/x86 is probably the
> > >wrong choice. I suggest that you try with Linux and compare. We'd be
> > >interested to hear of your results.
> >
> > Linux? uhhh.....yea.....
> >
> > Well I have been an OpenBSD guy, but I like the journaling of Solaris, but
> > I also maintain serveral sparc machines (solaris is the only OS that truly
> > seems to run uninhibited on sparc) ...so I am very familiar with this OS.
>
>:-)
>
>I'm sure you have your reasons for the choice, -- but you were asking
>for performance. :-) I don't know of how much Solaris/x86 has been
>improving, but when I tried 2.5 some years back it was several times
>slower than Linux 2.0.x at this type of task (and somewhat slower on
>all other tasks).
>
>If I really wanted popa3d to have the best possible performance on
>Solaris, I'd probably need to use mmap(2) and madvice(2) instead of
>those buffered reads which work better for other OSes. But the design
>decision was to avoid complicating the code with two implementations.
>And I'd expect it to be slower than the current code runs on Linux
>anyway.
>
>I currently have a Solaris/sparc and an OpenBSD/vax installs at home,
>but Linux is what I use for real.
Ok. Fair enough :)
FWIW, I am impressed. An older version I had tried of popa3d was very slow.
I had asked the list and I couldnt figure out what the trouble was.
On my system (at the time) qpopper was much faster at grabbing and popping
large spools.
(I know that makes no sense, but thats what it was for me...)
However, this version rocks :) - so it doesn't matter anymore!
qpopper was changing perms on my /var/mail to 660 and I didnt catch that
right away..so since the default mail.local delivers to user:group, anyone
with shell access could view someone elses email spool!! - so a work-around
I did was chmod g+sw /var/mail to root:mail and then tell mail.local to
deliver via GID mail. While this worked, it seems stupid to still have mail
files 660...
Instead of fixing the symptom on my system, I have now replaced qpopper and
fixed the PROBLEM.
Again, thanks for the excellent software. I installed it tonight on all the
machines I maintain (solaris of course) and there has not been a single issue.
--
J.D. Bronson
Aurora Health Care
Information Services
Milwaukee, Wisconsin USA
Main Office: 414.978.3000
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
