Re: BinkD Callback Service
  By: Tommi Koivula to Eric Renfro on Thu Oct 15 2015 07:09 pm

 TK> Eric Renfro - All wrote:

 > Michiel van der Vlist > wrote:

 >>> Hello Tommi,

 >>> How did you
 >>> do it? 

 >> I'm curious about this as well. I'm guessing a pearl script that we'd
 >> like to see.

 TK> Sorry Michiel, I forgot to answer this.

 TK> No perl. I'm using the old 4NT as command shell in Windows but this could
 TK> be done with cmd also.

 TK> In binkd.cfg:

 TK> exec "4nt.exe /c callback.bat *A0 *H" *test
 TK> overwrite test

 TK> Callback.bat;

 TK> echo node %1 -noproxy %2;[%2];* - c >>callback.log
 TK> echo node %1 -noproxy %2;[%2];* - c >callback.inc
 TK> echo log binkd-cow-callback.log >>callback.inc
 TK> echo sysname "COW Callback service" >>callback.inc
 TK> echo location "Calling %2" >>callback.inc
 TK> copy binkd.cfg binkd-cow-callback.cfg
 TK> type callback.inc >>binkd-cow-callback.cfg
 TK> binkd-cyg.exe -pP %1 binkd-cow-callback.cfg
 TK> echo # >callback.inc

 TK> That's it. ;)

Hmmm, well, that's not hard at all. In fact, I think I could immitate that
rather easily in Linux as well, without too much effort. I already have a
simple poll script that creates a simple .ilo file from a node address, and
that's essentially all it does, then that'll be gravy, but yet useful at the
same time, and without forcing an external client callout, but telling the
existing binkd server to callout on its own with it's own running clients just
waiting to perform. :)

)))[Psi-Jack -//- Decker]

... Everyone has his day, and some days last longer than others.
--- SBBSecho 2.27-Linux