Re: Re: Segfault when running wackamole in foreground

On Thursday, Oct 2, 2003, at 20:33 US/Eastern, Matthias Weidle wrote:
> --On Thursday, October 02, 2003 08:27:31 PM -0400 Theo Schlossnagle 
> <[email protected]> wrote:
>> On Thursday, Oct 2, 2003, at 19:15 US/Eastern, Matthias Weidle wrote:
>>> i dunno if it is breaking other things but i have experienced the 
>>> very
>>> same problem with segfaulting and i was able to fix that after
>>> compiling wackamole without thread support. i suppose the
>>> glibc/threadlib is to blame in that case ...
>>
>> I believe that is a stack space issue.  The release version of 
>> wackamole
>> requires and inordinately large stack size.  While that might be 
>> common
>> in unithread applications, it isn't in multithreaded applications.  I
>> think the CVS version has this problem fixed -- I'd love to know if
>> people still see the same problems with CVS HEAD.
>
>
> i would really love to try the latest HEAD of wackamole if only i 
> could login to the cvs server ...
>
> $ cvs -d :pserver:[email protected]:/data/cvs login
> Logging in to :pserver:[email protected]:2401/data/cvs
> CVS password:
> cvs [login aborted]: connect to cvs.omniti.com(66.80.117.4):2401 
> failed: Connection timed out
>
> anything wrong with it?

cvs.omniti.com doesn't run anon cvs.  But commedia.cnds.jhu.edu does.  
And on the backhand/wackamole page the CVSROOT is:

:pserver:[email protected]:/storage/cvs

That wasn't working though.  Server upgrade broke the chroot.  It is up 
now:

cvs -d :pserver:[email protected]:/storage/cvs login
<no password>
cvs -d :pserver:[email protected]:/storage/cvs co 
wackamole

// Theo Schlossnagle
// Principal Engineer -- http://www.omniti.com/~jesus/
// Postal Engine -- http://www.postalengine.com/
// Ecelerity: fastest MTA on earth