Hello All.

I mentioned before that my FidoNet outbound directory structure looks like this:

The tree of that directory looks like this:

-o-o-o-o-o-o-o-o-CUT-o-o-o-o-o-o-o-o-o-
+--Fido_Out
+--filehold
+--Out
+--018C002D.PNT
+--OUT.002
+--OUT.003
+--OUT.004
+--OUT.005
+--OUT.006
-o-o-o-o-o-o-o-o-CUT-o-o-o-o-o-o-o-o-o-


My binkd config for outbound looks like this:

domain fidonet Q:\\fido_out\\out 1

binkd does not seem to see the content of OUT.002 which looks like this:

-o-o-o-o-o-o-o-o-CUT-o-o-o-o-o-o-o-o-o-
The volume label in drive Q is Q_DRIVE.
The Volume Serial Number is E450:45BF.
Directory of Q:\FIDO_OUT\OUT.002

. <DIR> 12-20-20 3:16p
.. <DIR> 12-20-20 3:01p
011801D0 CUT 28682 12-20-20 3:16p
3 file(s) 28682 bytes used
2147450880 bytes free
-o-o-o-o-o-o-o-o-CUT-o-o-o-o-o-o-o-o-o-

What am I doing wrong? Irex has no problem seeing the entire BSO directory structure; surely there's something I'm omitting from or have written wrong in the configuration file(s).

Any help will be very much appreciated.


Best regards,
Marc

--- timEd/2 1.10.y2k+
* Origin: Sursum Corda! BBS-Huntsville,AL-bbs.sursum-corda.com (1:396/45)

Re: Even more questions!
By: Marc Lewis to All on Sun Dec 20 2020 03:21 pm

What am I doing wrong? Irex has no problem seeing the entire BSO directory structure; surely there's something I'm omitting from or have written wrong in the configuration file(s).

I am not sure why it's not being sent. Is there a node line in your config for the destination node?

I'm not sure if binkd is not seeing the outbound traffic, or if binkd doesn't know what to do with it.

Ttyl :-),
Al

... The answer is "maybe" ... and that's semi-final
--- SBBSecho 3.11-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757.2)

Hello Alan.

<On 20Dec2020 15:08 Alan Ianson (1:153/757.2) wrote a message to Marc Lewis regarding Even more questions! >

What am I doing wrong? Irex has no problem seeing the entire BSO
directory structure; surely there's something I'm omitting from or
have written wrong in the configuration file(s).

I am not sure why it's not being sent. Is there a node line in your
config for the destination node?

I'm not sure if binkd is not seeing the outbound traffic, or if
binkd doesn't know what to do with it.

It's evident that with me being in Zone 1, binkd either does not recognise the configuration line for that node, quoted below, or some other bizarre circumstance is preventing it from either sending or receiving from that node.

I fired up Irex again, and it not only sent all the mail waiting for Zone 2 but received a TON of .pkts from that node which had apparently been waiting for the last 2 or 3 days since I tried running binkd exclusively.

Here again is the first line of my binkd.cfg:
domain fidonet Q:\\fido_out\\out\\ 1

And the node's line in the NODES.CFG file:
node 2:280/464@fidonet fido.vlzn.nl (password) c

I also note that on that machine, which is substantially more powerful than this machine, binkd takes up over 96% of the processor, making the other programs and .cmd files quite lethargic. When it is running on this machine with just the 2 nodes that run on port 24555 (like I mentioned in a previous) message, it barely takes up 2% of the processor's resources. I am in a quandry about what to do with all these irregularities. Surely I have something configured incorrectly OR the bigger the number of nodes in the NODES.CFG the more idle resources it consumes, which is counterintuitive IMO. I'm obviously missing some point here.

Best regards,
Marc

--- timEd/2 1.10.y2k+
* Origin: Sursum Corda! BBS-Huntsville,AL-bbs.sursum-corda.com (1:396/45)

Re: Re: Even more questions!
By: Marc Lewis to Alan Ianson on Sun Dec 20 2020 06:40 pm

Here again is the first line of my binkd.cfg:
domain fidonet Q:\\fido_out\\out\\ 1

This is my domain line for fidonet..

domain fidonet /usr/local/fido/outbound 1

I wonder if the trailing "\\" in your domain line is needed, or if it makes a difference.

And the node's line in the NODES.CFG file:
node 2:280/464@fidonet fido.vlzn.nl (password) c

That looks good to me.

I also note that on that machine, which is substantially more powerful than this machine, binkd takes up over 96% of the processor, making the other programs and .cmd files quite lethargic.

That is a problem. Binkd on my machine also takes roughly 2% when idle and may spike up a bit when polling nodes but comes back down to 2% when done.

Just a suggestion, run binkd with the -d option and have a look at the output and see if everything looks as it should.

I am now running under linux but when I first ran binkd I was running under OS/2 and binkd ran great for me under OS/2 as it does under linux.

Ttyl :-),
Al

... I may not be perfect, but parts of me are excellent.
--- SBBSecho 3.11-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757.2)

Hello All.

<<Following up a message from Marc Lewis to Alan Ianson about Re: Even more questions! >>

What am I doing wrong? Irex has no problem seeing the entire BSO
directory structure; surely there's something I'm omitting from or
have written wrong in the configuration file(s).

I am not sure why it's not being sent. Is there a node line in your
config for the destination node?

I'm not sure if binkd is not seeing the outbound traffic, or if
binkd doesn't know what to do with it.

It's evident that with me being in Zone 1, binkd either does not
recognise the configuration line for that node, quoted below, or
some other bizarre circumstance is preventing it from either
sending or receiving from that node.

I fired up Irex again, and it not only sent all the mail waiting
for Zone 2 but received a TON of .pkts from that node which had
apparently been waiting for the last 2 or 3 days since I tried
running binkd exclusively.

[SNIP]

Here's the f@@@ing problem!

BINKD2KLIBC-ZLIB-BZLIB2.EXE <<<<<<<<WORKS LIKE A CHAMP!
BINKD2KLIBC.EXE <<<<<<<<<<<<<<< BROKEN BADLY!

If that one got any worse, it would have locked up the entire machine. Not only can it NOT see the Zone 2 outbound files, it does not do the "printq" nor the "percents" and probably half-a-dozen other quirks. What a FREAKING WASTE OF TIME! In FidoNet terms "Excessively Annoying."

Best regards,
Marc

--- timEd/2 1.10.y2k+
* Origin: Sursum Corda! BBS-Huntsville,AL-bbs.sursum-corda.com (1:396/45)

Hi Marc,

On 2020-12-20 15:21:57, you wrote to All:

I mentioned before that my FidoNet outbound directory structure looks
like this:

The tree of that directory looks like this:

-o-o-o-o-o-o-o-o-CUT-o-o-o-o-o-o-o-o-o-
+--Fido_Out
+--filehold
+--Out
+--018C002D.PNT
+--OUT.002
+--OUT.003
+--OUT.004
+--OUT.005
+--OUT.006

Wow! You still have outbound directories for the Zones 5 and 6 that have been abolished a long time ago! Are there any files in it? ;)

My binkd config for outbound looks like this:

domain fidonet Q:\\fido_out\\out 1

Directory of Q:\FIDO_OUT\OUT.002

I guess, the OS/2 file system isn't case sensitive?


Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

Hi Marc,

On 2020-12-20 18:40:56, you wrote to Alan Ianson:

And the node's line in the NODES.CFG file:
node 2:280/464@fidonet fido.vlzn.nl (password) c

# * Flavour is one of i, c, d, -, h; and is the flavour for the outbound
# filebox ("obox").

So you don't need to specify that last 'c' in your config. It's only needed when you use a filebox (and you shouldn't).


Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

Hi Marc.

21 Dec 20 00:36:40, you wrote to All:

BINKD2KLIBC-ZLIB-BZLIB2.EXE <<<<<<<<WORKS LIKE A CHAMP!
BINKD2KLIBC.EXE <<<<<<<<<<<<<<< BROKEN BADLY!

Which executables these are? What does -vv tell?

'Tommi

---
* Origin: - rbb.fidonet.fi - Finland - (2:221/1)

Hello Tommi.

<On 22Dec2020 10:03 Tommi Koivula (2:221/1) wrote a message to Marc Lewis regarding Follow-up on: Even more questions! >

21 Dec 20 00:36:40, you wrote to All:

BINKD2KLIBC-ZLIB-BZLIB2.EXE <<<<<<<<WORKS LIKE A CHAMP!
BINKD2KLIBC.EXE <<<<<<<<<<<<<<< BROKEN BADLY!

Which executables these are? What does -vv tell?

I deleted the bad executable. Here's the version on the good one:

-o-o-o-o-o-o-o-o-CUT-o-o-o-o-o-o-o-o-o-
[c:\binkd]binkd -vv
Binkd 1.1a-111 (Dec 13 2020 01:00:09/OS2)
Compilation flags: gcc (klibc), zlib, bzlib2, https, ntlm, amiga_4d_outbound, [line wrap]bwlim.
Facilities: fts5004 rfc2553emu
-o-o-o-o-o-o-o-o-CUT-o-o-o-o-o-o-o-o-o-

Best regards,
Marc

--- timEd/2 1.10.y2k+
* Origin: Sursum Corda! BBS-Huntsville,AL-bbs.sursum-corda.com (1:396/45)