Thanks digital man for providing the XSDK, that sure is slick and made some things I was working on a lot easier than I expected!
Tonight I spent some time updating the source to an old linux console curses based game to use the XSDK and data available in the xtrn.dat drop file instead of using command line parameters or the linux environment.
For the most part, that works well, but I do get a STDERR whenever calling the program, even though the program seems to operatore correctly.
!XSDK Error -1 (9) sending on socket 28
The number in paranthesis may change, last time I ran the door that number was (88).
Is this something I should worry about? I can eliminate the message by redirecting STDERR to a log file, but if there is a better/correct method to eliminate this, I'm interested.
How do you have "Intercept I/O" option set for your door in SCFG? For XSDK, it should normally be set to "No". It sounds like you may have it set to "Standard" instead.
facepalm<
Re: XSDK error writing to socket
By: Digital Man to Hemo on Thu May 26 2016 01:12 am
How do you have "Intercept I/O" option set for your door in SCFG? For XSDK, it should normally be set to "No". It sounds like you may have it 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..
The case (upper or lower) of the drop file is configurable in SCFG. You apparently have it configured to drop a lowercase xtrn.dat.
Re: XSDK error writing to socket
By: Digital Man to Hemo on Thu May 26 2016 03:54 pm
The case (upper or lower) of the drop file is configurable in SCFG. You apparently have it configured to drop a lowercase xtrn.dat.
there is that. this is what I get for not paying attention when trying multiple things. I likely had it set to upper case initially, and then somewhere along the lines of trying to debug the other issue, changed this to lower case.
I might adjust the #ifdef I added and have the XSDK look for upper case first, and then if on linux, also check for lower case if upper case is not found before giving up. That might save me from memory fog in a few months.
The case (upper or lower) of the drop file is configurable in SCFG. apparently have it configured to drop a lowercase xtrn.dat.
there is that. this is what I get for not paying attention when trying multiple things. I likely had it set to upper case initially, and then somewhere along the lines of trying to debug the other issue, changed thi to lower case.
I might adjust the #ifdef I added and have the XSDK look for upper case first, and then if on linux, also check for lower case if upper case is n found before giving up. That might save me from memory fog in a few mont
Using fexistcase(), from xpdev, would be the better solution.
Sysop: | echicken |
---|---|
Location: | Toronto, Ontario |
Users: | 2,224 |
Nodes: | 6 (0 / 6) |
Uptime: | 13:35:59 |
Calls: | 14,143 |
Files: | 295 |
Messages: | 551,295 |