Subj : Binkd tools (TIC, FREQ's...), gating, and setup To : Alan Ianson From : rick christian Date : Wed Sep 28 2016 09:42 am On 09/24/2016 12:39 AM, Alan Ianson -> rick christian wrote: AI> It works well in my setup since binkd is daemonized it is always listening AI> and watching the outbound all I need to do is touch the flow file of the AI> node I want to poll and I'm done. I don't need to start another binkd. binkd starts via init.d script for the "production" node that is setup awaiting a number... The "testing" node has had the latest package corrected to install and then a little updates and it will run on 14.04 basically update-rc should do it, but since I did that and changed the user for the init.d script at the same time it may need that too... when I reboot this one it starts just like the normal installed repo version does. I am going to write up a little FAQ and offer the DEB up as soon as I get things settled. I'll figure out what the depends that I removed is doing later to hopefuly fix the manual fix that is needed to get it to start up... It appears from glancing at it based on the fix that the commands to update-rc changed between 14.04 and 15+ due to the systemd plaque ... which on 14.04 you don't need but it seems to effec the upstart stuff.. I'll look at it later to try to fix it so you don't need the "manual" fix. BUT doing binkd -qpP1:135/0 just makes it mad... and does nothing. rc>> binkd -nP1:135/0 ~/fido/binkd/binkd.cfg AI> Ahh.. I haven't used -n before that I remember. That might work better for AI> what you are doing. If that does what you need to do add a cron entry that AI> does that. That is the only way that "works" as *I* expect it to. And keeps binkd from going nuts. AI> It's still what we need to do. I suppose now that there are no tolls we can AI> poll at will and I usually crash everything to the destination. For the majority since at least in Z1 its net based and most binkp... Although I am going to play with something to see if that works to do something still net based.. but in a more familar way for me. Its more of project to see what might happen in regards to this.... AI> Yep, just make and install what you need and your done.. :) Sorry, but you and others keep repeating that, and from that movie.. "I don't think that means what you think it does!" :) ;) There appears to be very SPECIFIC rules which are hidden away in some crevice I am not finding, or in some other language.. And that certainly was not the case... AI> It's important what order you install things.. areafix before hpt etc. URRRGHHHHHHHHHHHHHHHHHHHHHHHHH!!! Where are all these "RULES!!!???"!!!!!!!!!!! ???????????????? That is NOT in the install text, and the other message I have just lists to make this stuff AFTER doing something else huskylib, huskybase, xsmpai fidoconf then do the other stuff like hpt etc... That means pretty much what did compile when I did, is worthless then, as I didn't go in that order... URRRGHHHHHHHHHHHHHHHHHHHHHHHHH!!! I think that VM is trashed anyway since syncterm just barfed all over it.... who knows.. So SPECIFICALLY what order is this stuff supposed to be done in???? sudo apt-get build-essential (+20 suggests) packages then get husky source tar -xvf husysource cd huskysource cd huskylib ..... cd huskybse ..... cd xsmapi ..... cd fidoconf ...... AI>> Both of those are freqable from the authors or I can plonk what I have AI>> here in your inbound for you to look over. I'll look them over for the production node once node number and echos are flowing there... THANKS! * Origin: news://news.wpusa.dynip.com | acct req'd to post (1:3634/12) .