Subj : Semaphores.
To   : j b l
From : mark lewis
Date : Thu Mar 09 2017 10:12 am


 On 2017 Mar 09 02:40:34, you wrote to me:

 ML>> to create a "flag file" you would use the "flag" keyword similar to
 ML>> the following...

 ML>> flag x:\\foo\\semaphore\\mail-in.sem *.su? *.mo? *.tu? *.we? *.th?
 ML>> *.fr? *.sa? *.pkt *.tic

 jl> How would I pass the tosser/scanner to this line?

after the session is over, binkd will create the file 
x:\foo\semaphore\mail-in.sem... you need another process to watch for that 
semaphore... when it appears, start your mail tossing routine... remember to 
set another semaphore to prevent mail tossing from running more than one at a 
time... you should also remove this mail-in.sem since it has done its 
business...

eg:
rem ** mail tossing script **
rem first check if we are already running
rem if so, just exit out the bottom
if exist x:\foo\semaphore\tossing.sem goto end
rem tell others that we're running
echo.>x:\foo\semaphore\tossing.sem
rem remove the semaphore that started us
del x:\foo\semaphore\mail-in.sem
rem do tossing stuff here
rem do more tossing stuff here
rem all done so now we can remove our semaphore
del x:\foo\semaphore\tossing.sem
:end
rem that's all folks!


i wrote that on the fly as a simple .bat file... i'm not sure which side you 
need this on... if you are working on the linux side of the fence, you might be 
able to get fancy and just monitor the datetime of the semaphore rather than 
having to delete it... it is possible to have a race condition but it isn't 
that bad for this process... the tosser generally has its own mechanism to 
prevent it from running more than once at a time... these semaphores are to 
start this process and prevent the script from running more than once...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it 
wrong...
.... Kansas is just a giant concentration camp for cattle.
---
 * Origin:  (1:3634/12.73)

.