Subj : binkd.conf
To   : j b l
From : mark lewis
Date : Fri Mar 10 2017 10:23 am


 On 2017 Mar 09 20:59:46, you wrote to me:

 ML>> you're doing it twice... choose one or the other for your tossing...
 ML>> either use a semaphore to signal the toss needs to be done at some
 ML>> point in time OR execute the toss script directly... one or the
 ML>> other...

 jl> If I go the semaphore route, how will it know when to use the
 jl> tosser/scanner? It isn't defined in the "flag" line..

binkd doesn't care... it doesn't need to know for a simple disk-based flag file 
(aka semaphore)... all it does is create the file... that other process i spoke 
of that would handle your tossing would need to know, though... it would be a 
stand-alone looping script or a single-shot one fired by cron every so often...

if you already have a script to toss inbound mail, you could easily let cron 
fire it off and have it look for the mail-in.sem before thinking about doing 
any work... it should create its own semaphore (eg: tossing.sem) so that it 
won't run more than once at a time... this would be your single-shot script i 
mentioned before... using the methods i demonstrated in that sample script the 
other day...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it 
wrong...
.... Now I definitely crave a pork product of some kind.
---
 * Origin:  (1:3634/12.73)

.