From: immortal@IDOMAIN.remove-ii7-this

Should synchronet be cleaning up the node temp dirs after returning from a door, or after a caller disconnects?

I'm having a problem where randomly DOSEMU doors will refuse to run. The log shows the door is executing as normal but on the remote terminal either nothing
appears to happen, or one of my sunrise doors loads in ascii mode and says I am
out of time and
exits.

If I look in my /sbbs/node1 dir, I have a DOOR.SYS, door.sys, DOOR32.SYS, XTRN.DAT, etc. Most of which are old, from previous calls. I'm assuming DOSEMU is getting confused with having both a door.sys and DOOR.SYS in the same
directory. I couldn't get
any doors to load today until I deleted all the drop files out of the directory
and then ran a door, it created a fresh door.sys and then the door loaded properly.

Should I put in a cleanup command to delete the drop file in each door configuration? It would seem easier/cleaner to have synchronet automatically do this upon returning from a door.

Thanks

Immortal

... Anything that keeps a politician humble is healthy for democracy.

---
þ Synchronet þ Immortal's Domain
--- Synchronet 3.17c-Win32 NewsLink 1.110
* Vertrauen - Riverside County, California - telnet://vert.synchro.net

--- SoupGate-Win32 v1.05
* Origin: www.darkrealms.ca (1:229/2)

From: digital.man@vert.synchro.net.remove-owg-this

To: Immortal
Re: Node temp dirs
By: Immortal to All on Mon Aug 19 2019 07:16 pm

Should synchronet be cleaning up the node temp dirs after returning from a door, or after a caller disconnects?

It should and does.

I'm having a problem where randomly DOSEMU doors will refuse to run. The log shows the door is executing as normal but on the remote terminal either nothing appears to happen, or one of my sunrise doors loads in ascii mode and says I am out of time and exits.

If I look in my /sbbs/node1 dir, I have a DOOR.SYS, door.sys, DOOR32.SYS, XTRN.DAT, etc. Most of which are old, from previous calls. I'm assuming DOSEMU is getting confused with having both a door.sys and DOOR.SYS in the same directory. I couldn't get any doors to load today until I deleted all the drop files out of the directory and then ran a door, it created a fresh door.sys and then the door loaded properly.

Ah, good catch. The node directory is not really a "temp directory", so it is not cleaned-up (all files deleted), ever.

Should I put in a cleanup command to delete the drop file in each door configuration? It would seem easier/cleaner to have synchronet automatically do this upon returning from a door.

I just committed a fix to xtrn_sec.cpp. Give it a shot.

Thanks for the detailed bug report,

digital man

Synchronet/BBS Terminology Definition #84:
XSDK = Synchronet External Program Software Development Kit for C/C++
Norco, CA WX: 81.5øF, 46.0% humidity, 10 mph ENE wind, 0.00 inches rain/24hrs --- Synchronet 3.17c-Win32 NewsLink 1.110
* Vertrauen - Riverside County, California - telnet://vert.synchro.net

--- SoupGate-Win32 v1.05
* Origin: www.darkrealms.ca (1:229/2)

From: nightfox@DIGDIST.remove-mdg-this

To: Immortal
Re: Node temp dirs
By: Immortal to All on Mon Aug 19 2019 07:16 pm

Should synchronet be cleaning up the node temp dirs after returning from a door, or after a caller disconnects?

I'm having a problem where randomly DOSEMU doors will refuse to run. The log shows the door is executing as normal but on the remote terminal either nothing appears to happen, or one of my sunrise doors loads in ascii mode and says I am out of time and exits.

If I look in my /sbbs/node1 dir, I have a DOOR.SYS, door.sys, DOOR32.SYS, XTRN.DAT, etc. Most of which are old, from previous calls. I'm assuming DOSEMU is getting confused with having both a door.sys and DOOR.SYS in the same directory. I couldn't get any doors to load today until I deleted all the drop files out of the directory and then ran a door, it created a fresh door.sys and then the door loaded properly.

Should I put in a cleanup command to delete the drop file in each door configuration? It would seem easier/cleaner to have synchronet automatically do this upon returning from a door.

I ended up creating a batch file that will clean up drop files after a door exits. I think it's a good thing to do, to avoid problems such as the one you're seeing.

Nightfox

---
þ Synchronet þ Digital Distortion: digitaldistortionbbs.com
--- Synchronet 3.17c-Win32 NewsLink 1.110
* Vertrauen - Riverside County, California - telnet://vert.synchro.net

--- SoupGate-Win32 v1.05
* Origin: www.darkrealms.ca (1:229/2)

From: immortal@IDOMAIN.remove-i77-this

To: Digital Man
Re: Node temp dirs
By: Digital Man to Immortal on Mon Aug 19 2019 06:35 pm

Re: Node temp dirs

I just committed a fix to xtrn_sec.cpp. Give it a shot.

Thanks for the detailed bug report,

Will do. Thanks for the quick fix!

Immortal

... Think like a man of action, act like a man of thought.

---
þ Synchronet þ Immortal's Domain
--- Synchronet 3.17c-Win32 NewsLink 1.110
* Vertrauen - Riverside County, California - telnet://vert.synchro.net

--- SoupGate-Win32 v1.05
* Origin: www.darkrealms.ca (1:229/2)