TIP: Click on subject to list as thread! ANSI
echo: fidosoft.husky
to: mark lewis
from: Nicholas Boel
date: 2016-12-22 23:16:54
subject: Bug report.

Hello mark,

On Thu Dec 22 2016 17:46:54, mark lewis wrote to Nicholas Boel:

 NB>> However, when HPT stores the message into a JAM message base, it
 NB>> seems to round down to the next even number in seconds of when
 NB>> the message was written, if the message was originally posted
 NB>> with an uneven seconds in the timestamp.

 ml> ewwww... what message base format are we talking about?

JAM, with HPT as the tosser.

 ml> yeah, it shouldn't do that... it should round /up/ to the next even
 ml> second if the code is following the m$ DOS time stamp format
 ml> documentation...

That's not what seems to be happening. Since I'm using Linux, I would
assume I'm using the Linux "date" format. However, I have no idea
what method HPT is using, which is why I posted about it since something
isn't right. Obviously it would be a lot worse of a bug if it forwarded
messages the same way, but that has been proven otherwise.

Regards,
Nick

... "Не знаю. Я здесь только работаю."
--- GoldED+/LNX 1.1.5-b20161221
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)
SEEN-BY: 3/50 103/705 123/500 154/10 30 700 203/0 221/6 227/51 201 230/0
SEEN-BY: 240/1661 5832 249/303 261/38 280/464 5003 292/854 310/31 340/800
SEEN-BY: 423/120 633/267 280 640/384 712/550 848 770/1 2320/100 5075/35
@PATH: 154/10 280/464 712/848 633/267

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.