MSGID: 1:229/426 39E41019
On 12 Aug 15  11:31:10, Mark Lewis said the following to Nick Andre:

ML> those would be the .bsy files in the binkd outbound directories... dependin
ML> on the directory for the FTN domain and zone then the decode of the bsy fil
ML> name into two sets of hex and emitted as decimal... a bash script should be
ML> able to do this pretty easily... at least the zone:net/node numbers...
ML> determining the proper FTN domain will be tricky if 4D addressing is used
ML> since all will appear to be part of the main outbound domain...

I keep forgetting about those files... domain-processing I'm not really 
worried about in my particular case as I've got a fairly good set of code in 
place to manipulate the 4D-5D "conversion" when mail is moved out of DB into 
the BinkD FLO format.

As a side note, I wonder if the team would be amicable to just adding DB's 
Queue as a supported format internally. That would eliminate a HUGE amount of 
code in the mailer for me... as I'm sure you could understand.

But those BSY files do not get periodically updated with tranmission rates,
sent/received, etc? Thats really what I'm after. Its fine to tell a DB user 
whoes on, but would be better if I could give them a sneak-peak of the 
traffic. Sortof the way that Internet Rex does it, graphically in ASCII.

ML> this paragraph caused me to look and see who i was communicating with :) 

LOL! In a good way I hope! I do my best work after a few beers :)

ML> yeah, a bash script wouldn't work but being able to code something in DB
ML> shouldn't be much different than DB's own semaphore monitoring and parsing,
ML> right?

Yes, the mailer's semaphore checking code happens every second. Very simple to
add whatever I want to check... as per above.

ML>  NA> A shutdown semaphore would be nice; in that if BinkD sees a particular
ML>  NA> semaphore, it will gracefully shutdown... rather than just being
ML>  NA> outright "killed" by an OS task maanger or shutdown process.
ML> 
ML> this (and other disk-based semaphores) have been asked for in the past... i
ML> wasn't well received... mainly because binkd originates on *nix which used 
ML> signaling method sending SIGHUP, SIGTERM, SIGKILL and others to the process
ML> to cause them to do certain things...

Thats understandable for *nix, but by the same theory that it is easy for me
to code semaphore-checking in my mailer, it should also in turn be easy to
code something that simply checks for that exit-file and gracefully shutdown.
Its no different of a graceful shutdown than when it is ran in "client" mode
and quits when its own queue is empty. Would be nice of the team to do this 
for "flavors other than *nix".

Nick

--- Renegade vY2Ka2