Subj : XSDK error writing to soc
To   : Digital Man
From : Hemo
Date : Sat May 28 2016 10:16:00

  Re: XSDK error writing to socket
  By: Digital Man to Hemo on Thu May 26 2016 01:12 am

 DM> How do you have "Intercept I/O" option set for your door in SCFG? For
 DM> XSDK, it should normally be set to "No". It sounds like you may have it
 DM> set to "Standard" instead.

oh.. it got better than that the more I fiddled with things...

I narrowed it down to xsdk.c and the presence of pre-existing XTRN.DAT files in
the node directorys when I did the initial pull to build the system.

xsdk.c is looking for XTRN.DAT in the node directory, and on CentOS - the
system is writing out xtrn.dat files.  Whatever settings were in the XTRN.DAT
must have been causing things, and I honestly can't say how the program was
starting any longer, unless I was connected to a different node and that file
had slightly different settings... once I removed the XTRN.DAT files I would
then catch a glimpse that the system couldn't find file /sbbs/node1/XTRN.DAT

>facepalm<

I made an edit to xsdk.c :
#if defined(__unix__)
        sprintf(str,"%sxtrn.dat",node_dir);
#else
        sprintf(str,"%sXTRN.DAT",node_dir);
#endif

I have needed to make a few other edits in the xsdk as well, some conflicts
with getch and getstr between the xsdk and curses,it seems.

Things are better, I'm off to the next step of my project..

---
 þ Synchronet þ - Running madly into the wind and screaming - bbs.ujoint.org
 þ wcQWK 7.0 ÷ ILink * Omicron Theta * Southaven MS * winserver.org

--- QScan/PCB v1.20a / 01-0462
 * Origin: ILink: CFBBS | cfbbs.no-ip.com | 856-933-7096 (454:1/1)

.