sks-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Sks-devel] Re: sks recon cores when it claims "reconciliationcompl


From: Yaron Minsky
Subject: Re: [Sks-devel] Re: sks recon cores when it claims "reconciliationcomplete"
Date: Tue, 27 Jan 2004 11:21:11 -0500 (EST)
User-agent: SquirrelMail/1.4.2-1

Hmmm.  that is weird.  Segfaults, even if ultimately avoidable, make me
unhappy.  I've started doing a bignum port, and it's going pretty well. 
It will be slower, but I'm not too worried about that.  I'll report on
this as I make progress.

y

Chris Kuethe said:
> On Mon, 26 Jan 2004, Yaron M. Minsky wrote:
>
>> So, it sounds like Numerix is at fault.  One interesting thing about
>> Numerix is that it has 3 different implementations: Slong, based on an
>> assembler/C core, Dlong, which uses long-longs (this only works on
>> 32-bit machines) and Clong, which is supposed to be broadly portable.
>
> More wierdness, I just switched back to Slong, and restarted with a
> totally clean database and it works. I had a separate sks process
> running on its own disk just doing a load. It finally finished, and
> I just copied that into my server directory and now reconciliation works.
>
> Still, that's not necessarily desirable behaviour - requiring most of
> the database to be sent to the clients before reconciliation can begin.
> It'd be interesting to see what happens with Ocaml's own bignum support.
>
> CK
>
> --
> Chris Kuethe, GCIA CISSP: Secure Systems Specialist - U of A CNS
>       office: 157 General Services Bldg.    +1.780.492.8135
>               address@hidden
>
>      GDB has a 'break' feature; why doesn't it have 'fix' too?
>
>
>
> _______________________________________________
> Sks-devel mailing list
> address@hidden
> http://mail.nongnu.org/mailman/listinfo/sks-devel
>


|--------/            Yaron M. Minsky              \--------|
|--------\ http://www.cs.cornell.edu/home/yminsky/ /--------|

Open PGP --- KeyID B1FFD916
Fingerprint: 5BF6 83E1 0CE3 1043 95D8 F8D5 9F12 B3A9 B1FF D916





reply via email to

[Prev in Thread] Current Thread [Next in Thread]