On Wed, 29 Oct 2014, Bj”rn Felten wrote to mark lewis:

 ml> set the cronjob to run every minute, or five minutes or whenever...

 BF>    I was hoping for a more elegant way,

sadly, that is elegance in today's world... definitely what one has to do in
the *nix world since they also don't seem to have any schedulers that react
when a semaphore is created... you gotta waste resources firing a script and
letting it look to see if there's anything for it to do...

 BF> but if there's no semaphore file for Argus that does the job (like 
 BF> e.g. the semaphore file for nodelist update), I guess that's my 
 BF> only option. :(

argus doesn't exit for the nodelist compilation... it uses its internal
compiler... it doesn't know anything about tossing mail so you would have to
trigger it externally anyway... if argus could detect the semaphore, the best
it could do might be to trigger the external tossing script or possibly create
another semaphore to start it by some other means but since it doesn't, you
have to use something else...

you don't even have to use argus' cron to fire a scheduled job if you have
something else that can fire tasks when they see a semaphore... on OS/2 i use
wcron which is one of the only schedulers i've found that can do this... i
have no clue what else may be available... only that there's no reason to get
the mailer involved other than possibly firing a scheduled cron job... you
could use some other scheduler to fire the script, too... even the windows one
if that's the world your system is operating in...

i've even seen systems that have a script that runs all the time from
startup... the script basically sleeps all the time and wakes occasionally to
look for a semaphore before executing the task or going back to sleep...

you'd have this same ""problem"" if you were running binkd, too...

kinda makes one miss the days of traditional mailers with their features and
advanced capabilities, eh? ;)

)\/(ark

 * Origin:  (1:3634/12)