Hello Bob!

10 Sep 03 09:24, you wrote to me:

 BJ> Hello, Bo...  Sorry for the delay in response....  I'm dealing with a
 BJ> neighbor who had a stroke and has a disabled son.....  (along with my
 BJ> parents).....  Free time will be short thru the end of the month....

Okay.

 BJ>> Hmmmm.....  My setup seems to be eating some messages between
 BJ>> 1:343/41 and 1:343/40....  Or, I didn't catch this one on
 BJ>> 1:343/40.....  Need to look closer. I believe BinkD is *not*
 BJ>> properly handling failures on writing (or renaming) files when
 BJ>> received.....

 BS>> Just a problem i thought of.. if the reciever system
 BS>> isn't tossing regulary, and squish calls the packages
 BS>> the same filename, what is the mailer supposed to do?

 BJ> The standard file names I'm using shouldn't overwrite until the eighth
 BJ> day.  And even then, squish should only be adding to existing
 BJ> archives, the way I'm set up....  I suspect I have a mailer on
 BJ> 1:343/41 still configured to send 1:343/40 to 1:343/41 or something
 BJ> like that, or maybe a squish configuration file burried some place
 BJ> (for daily or weekly cleanup) that still hasn't had the 1:343/41 vs
 BJ> 1:343/40 nodes seperated since at one point the two nodes had been
 BJ> merged together in the past.....

Okay, I didn't have any sort of problems, maybe because my links is
connection to me nearly every day.

 BJ> There may also be a "point" issue,
 BJ> due to how I've also used some point numbers for cross connecting the
 BJ> two systems before merging the two nodes in the past.....  And now I'm
 BJ> trying to break back to using the two node numbers on seperate
 BJ> machines.....  I just need time to look for the issue.  This just
 BJ> impact the experimental machine for now....

Okay.

 BS>> Maybe squish should use sprintf(arcname, "%08x.%s",
 BS>> time(NULL), ...); for arcmail filenames..

 BJ> No reason to change from the existing standard .... at least not
 BJ> yet....

Well if the filenames is getting duped, within a week, there is.

 BS>>>> Did anyone of you notice that the CVS version of maximus
 BS>>>> segfaults?

 BJ>>> Do you mean when running with a telnet port?  Or via the local
 BJ>>> console (with the -k option)?

 BS>>> With the telnet port.

 BJ>> Ok.  The telnet port broke on my system a few weeks ago.  I think
 BJ>> Wes made a check in of some code related to getting serial /
 BJ>> modem support, but I haven't dug into the logs enough to make
 BJ>> sure of my suspision.  I'll have to try your suggested roll back
 BJ>> to see if it clears up the problem here.  'bin/max -k' is running
 BJ>> ok on 1:343/40.  The runbbs.sh script (using telnet) bombs out on
 BJ>> 1:343/40 like I believe it is / was doing on your system....

Okay, do you have ansi graphics on max -k (more than two colors).

 BS>> I bet it's the same, if you run max -w what's happingen then?

 BJ> I get a setmentation fault when using the -w switch on my current
 BJ> version under linux.  It's been a few weeks since I've update code
 BJ> from CVS....

Indeed, use the old libcompat.so and the old libcomm.so

 BS>> Hmm.. i didn't tested the editor in local mode.. Local
 BS>> mode is a bit wierd, because i only see monocrome
 BS>> colors.. maybe my config is wrong?

 BJ> Yes, I'm seeing monochrome on local mode also.  I haven't investigated
 BJ> why, but I'm sure it is due to how the console is emulated.....

Okay, BTW I fixed the filetransfer issue today, and QWK (only download).

 BS>>> :-) Maybe we could put the old version on CVS, so
 BS>>> people can get something there _works_.

 BJ>> Yes!  Since the .so files are generated by the make files, we
 BJ>> need to track it back to which source files changed, check in the
 BJ>> bad code as a branch, and re-check in the good code on the main
 BJ>> line. I won't get to this today.....

 BJ> Nor have I had the time the last few weeks, or the next few weeks.  :(
 BJ> Hopefully I'll use this message as a reminder when I get some free
 BJ> time....

Good.

Regards,
Bo

... The important thing is not to stop questioning. ð- Albert Einstein
--- GoldED+/LNX 1.1.4.7