Alprunty wrote to All <=-
When I run Bink-d I get this. I just want it to poll the filegate to
know it's working.
Allen
--0-0-000
C:\sbbs\binkd>binkd-static.exe binkd.cfg
20:36 [3700] binkd.cfg: line 18: error in configuration files idoinbsecure: incorrect directory
Cannot open C:sbbinkinkd.log: Invalid argument!
! 20:36 [3700] error in configuration, aborting
Cannot open C:sbbinkinkd.log: Invalid argument!
C:\sbbs\binkd>? 20:36 [3700] C:sbbs
===================
My config is as follows.
domain fidonet C:\sbbs\fido\outbound 1
domain fido alias-for fidonet
domain fidonet.org alias-for fidonet
address 1:2320/100@fidonet
sysname "LiveWire BBS"
location "Louisville, KY"
sysop "Allen Prunty"
nodeinfo 300,TCP,BINKP
connect-timeout 60
try 10
hold 600
send-if-pwd
log C:\sbbs\binkd\binkd.log
loglevel 4
percents
printq
backresolv
inbound C:\sbbs\fido\inbsecure
inbound-nonsecure C:\sbbs\fido\inbound
temp-inbound C:\sbbs\fido\incomplete
minfree 2048
minfree-nonsecure 2048
kill-dup-partial-files
kill-old-partial-files 86400
kill-old-bsy 43200
flag C:\sbbs\data\fidoin.now *.pkt *.PKT
flag C:\sbbs\data\fidoin.now *.su? *.mo? *.tu? *.we? *.th? *.fr? *.sa? *.SU? *.MO? *.TU? *.WE? *.TH? *.FR? *.SA?
prescan
node 1:261/38@fidonet -md filegate.net
echicken wrote to Alprunty <=-
20:36 [3700] binkd.cfg: line 18: error in configuration files idoinbsecure: incorrect directory
Cannot open C:sbbinkinkd.log: Invalid argument!
Look at those messages for a while, compare them to your config file,
and you might see a pattern to the output.
You'll want to either escape your backslashes in the paths in the
config file, or use slashes (forward slashes) instead, eg: 'c:\\sbbs\\bink\\binkd.log' or 'c:/sbbs/bink/binkd.log'.
Tony Langdon wrote to Bill McGarrity <=-
Bill McGarrity wrote to Alprunty <=-
Alprunty wrote to echicken <=-
Re: Bink D --- HELP!!! Don't know what I'm missing
By: echicken to Alprunty on Fri Apr 22 2016 08:45 pm
'c:\\sbbs\\bink\\binkd.log' or 'c:/sbbs/bink/binkd.log'.
Why are we double slashing?
binkd uses a linux style cfg file which doesn't have the same directory structure as a win based system.,... therefore the double slash when
using backslashes. Trust us, it works.. :)
Looks like binkd interprets its config in a similar way to shells such
as Bask, so the first backslash is an escape character, the second
tells the parser that the character to read is a backslash. Those of
us familiar with mixing Windows and Linux will have seen this before.
For example, when mounting SMB/CIFS shares on a Linux box.
| Sysop: | digital man |
|---|---|
| Location: | Riverside County, California |
| Users: | 1,042 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 01:01:14 |
| Calls: | 500,919 |
| Calls today: | 6 |
| Files: | 109,372 |
| D/L today: |
15,743 files (2,415M bytes) |
| Messages: | 305,068 |
| Posted today: | 7 |