Message Area
Casually read the BBS message area using an easy to use interface. Messages are categorized exactly like they are on the BBS. You may post new messages or reply to existing messages!

You are not logged in. Login here for full access privileges.

Previous Message | Next Message | Back to Support Echo For JAMNNTPD NNTP S...  <--  <--- Return to Home Page
   Networked Database  Support Echo For JAMNNTPD NNTP S...   [95 / 238] RSS
 From   To   Subject   Date/Time 
Message   mark lewis    Rick Christian   crashmail Echo JAM Base - Errors and Exporting   November 4, 2016
 6:17 PM *  

04 Nov 16 13:46, you wrote to Matt Bedynek:

 MB>> When I started trying to setup jamnntpd here I noticed that when
 MB>> posting messages it would corrupt a message base or not see all the
 MB>> messages.  I concluded it was an alignment error because the int's
 MB>> used in the library are not of size specific.  the sizeof an int can
 MB>> vary on architectures..  So when jamnntp's jamlib is built on a 64
 MB>> bit platform some of them are wrong size.

 MB>> It wouldn't take much to go thru the code and fix this, or simply
 MB>> build it with -m32 option (which I tested and works fine).

 RC> DING!! DING!!

 RC> Well you have spilled the beans as it were.. I've been digging through
 RC> that circular bug mess on this exact issue..

i don't recall you saying anything about 64bit :(  i hope this alignment stuff
makes it into the rest of the code bases soonish... i was actually
contemplating taking my code on my production OS/2 box and copying it over to
my 64bit ubuntu box and letting it fly... i will thank you for stepping into
that mess and bringing the bitness problem to light... i have to wonder who
else has fallen into that trap without knowing it? rossC over at 123/500 has a
very popular jamnntpd server and there has been some weirdness problems there
that may be due to this bitness stuff... i don't know and i don't know what
bitness he has compiled his jamnntpd for... he does use HPT for his tosser,
IIRC... i think it does 32bit and 64bit as i'm using it on this 64bit ubuntu
box and i compiled HPT here with no bitness stuff specified...

[trim]

 RC> So is the V1.3 code at the SF stuff *correct* for *64b* operation or
 RC> no one knows as for some reason every one is using 32b??? And the only
 RC> other working server user seems to be using OS/2 ... although his bug
 RC> patch was added to the V1.3 code on 9/10/16.....

i don't know which bug patch that was... i posted several of them to this echo
over a couple of weeks... i haven't been back into the code since then... i
also hope you aren't mixing me up with jame or anyone else... jame is the one
managing the ftnapps repo...


)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it
wrong...
... Care for a shrimp cocktail? No, thanks - I need a BIG one.
---
 * Origin:  (1:3634/12.73)
  Show ANSI Codes | Hide BBCodes | Show Color Codes | Hide Encoding | Hide HTML Tags | Show Routing
Previous Message | Next Message | Back to Support Echo For JAMNNTPD NNTP S...  <--  <--- Return to Home Page

VADV-PHP
Execution Time: 0.0874 seconds

If you experience any problems with this website or need help, contact the webmaster.
VADV-PHP Copyright © 2002-2024 Steve Winn, Aspect Technologies. All Rights Reserved.
Virtual Advanced Copyright © 1995-1997 Roland De Graaf.
v2.0.140505

Warning: Unknown: open(c:\Sessions\sess_j9ntot86ac5eqji94lcodvf7s3, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\Sessions) in Unknown on line 0 PHP Warning: session_start(): open(c:\Sessions\sess_j9ntot86ac5eqji94lcodvf7s3, O_RDWR) failed: No such file or directory (2) in D:\wc5\http\public\VADV\include\common.inc.php on line 45 PHP Warning: Unknown: open(c:\Sessions\sess_j9ntot86ac5eqji94lcodvf7s3, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 PHP Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\Sessions) in Unknown on line 0