Re: sometimes tickit leaves the file in the incoming directory
By: Fernando Toledo to GitLab issue in main/sbbs on Sat Feb 17 2024 10:31 pm

Many times it happens to me that tickit after processing the file and moving it, it still remains in the incoming directory

Is it possible binkit is still running at the moment and might still have the file open?
--
digital man (rob)

Steven Wright quote #6:
A conscience is what hurts when all your other parts feel so good.
Norco, CA WX: 63.2øF, 61.0% humidity, 0 mph SW wind, 0.00 inches rain/24hrs
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

El 18/2/24 a las 18:12, Digital Man escribió:

Re: sometimes tickit leaves the file in the incoming directory
By: Fernando Toledo to GitLab issue in main/sbbs on Sat Feb 17 2024 10:31 pm

> Many times it happens to me that tickit after processing the file and moving
> it, it still remains in the incoming directory

Is it possible binkit is still running at the moment and might still have the file open?

=?
binkit run from sbbs (timed event) not as stand alone daemon.

If i understand, it trigger sbbsecho via semahore file and then sbbsecho
call tickit .. true?

sbbsecho also trigger binkit event via Outgoing Semaphore File binkout.now

I assume that 2 binkit instances are not running at the same time.
---
ï¿­ Synchronet ï¿­ Dock Sud BBS TLD 24 HS - bbs.docksud.com.ar
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Re: sometimes tickit leaves the file in the incoming directory
By: Ragnarok to Digital Man on Mon Feb 19 2024 01:00 am

El 18/2/24 a las 18:12, Digital Man escribi¢:

Re: sometimes tickit leaves the file in the incoming directory
By: Fernando Toledo to GitLab issue in main/sbbs on Sat Feb 17 2024 10:31 pm

> Many times it happens to me that tickit after processing the file and moving
> it, it still remains in the incoming directory

Is it possible binkit is still running at the moment and might still have the file open?

=?
binkit run from sbbs (timed event) not as stand alone daemon.

If i understand, it trigger sbbsecho via semahore file and then sbbsecho call tickit .. true?

No, SBBSecho doesn't call tickit, but it can touch a sem file that will cause Synchronet to run tickit.

sbbsecho also trigger binkit event via Outgoing Semaphore File binkout.now

I assume that 2 binkit instances are not running at the same time.

BinkIT can run via services (for incoming BinkP connections) and the timed event rhead (foru outgong BinkP connections), and these can happen at the same time.
--
digital man (rob)

Synchronet/BBS Terminology Definition #42:
IBM437 = Code Page 437 (so-called IBM Extended ASCII)
Norco, CA WX: 54.7øF, 94.0% humidity, 2 mph NE wind, 0.10 inches rain/24hrs
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

El 19/2/24 a las 22:00, Digital Man escribió:

No, SBBSecho doesn't call tickit, but it can touch a sem file that will cause Synchronet to run tickit.

> sbbsecho also trigger binkit event via Outgoing Semaphore File binkout.now
>
> I assume that 2 binkit instances are not running at the same time.

BinkIT can run via services (for incoming BinkP connections) and the timed event rhead (foru outgong BinkP connections), and these can happen at the same time.

I had forgotten that it runs as a service! exactly!
This could be causing that problem perhaps. =\
---
ï¿­ Synchronet ï¿­ Dock Sud BBS TLD 24 HS - bbs.docksud.com.ar
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)