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...   [96 / 238] RSS
 From   To   Subject   Date/Time 
Message   mark lewis    Rick Christian   crashmail Echo JAM Base - Errors and Exporting   November 5, 2016
 6:41 AM *  

04 Nov 16 14:12, you wrote to me:

 ml>> ahhh... 64bitness hasn't been indicated... i've been compiling my

 RC> I indicated that from the start Ubuntu server 14.0.4.5 *64b*

it wasn't prominent and repeated or otherwise made obvious... i'm on kubuntu
14.04.5 64bit here on this workstation and all the hosted VMs are ubuntu server
 but a mix of 32bit and 64bit... i've not yet attempted to build or run
jamnntpd on any of them but it has been considered... you posted a slew of
messages... many quite verbal but this being a 32bit vs a 64bit problem was not
 evident until now... ace in the hole? bullshit... if you knew this was the
problem causing your message base corruption, you should have said so from the
beginning...

it is also not a coding problem causing the different variable sizes between
32bit and 64bit... it is a declaration problem when the variables are
declared... it is only a problem because compiler maintainers made the bad
decision to change existing variable types and make them larger instead of
creating new types for them... new types had to be created any way so that
would not have been a problem and their decision has caused even more
problems... this situation is also not limited to C compilers... i've seen it
in pascal compilers, too... i'm sure it exists in many different languages as
well...

now, if someone would be so kind as to post what changes are needed for the
variable declarations so we don't need to worry about the arch or have to allow
 for multi-arch on 64bit systems, it would be a good thing... some folks like
to run pure 64bit with 32bit multi-arch totally disallowed and banned... i'm
surprised that you even allow 32bit on your 64bit setup... especially since you
 are so adamant about this and some political stuffs you've participated in...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it
wrong...
... "Gledlig jul og godt Nytt Aar." - Norse-Danish Christmas
---
 * 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.0905 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_jdj0ueadhguvqc76ajdhe8o523, 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_jdj0ueadhguvqc76ajdhe8o523, 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_jdj0ueadhguvqc76ajdhe8o523, 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