Subj : Re: File Request question
To   : Gamgee
From : Deuce
Date : Fri Dec 26 2025 07:19 am

  Re: Re: File Request question
  By: Gamgee to Deuce on Wed Dec 24 2025 02:21 pm

 >  De> Reading the wiki, the oddball way it's describing there, it's important
 >  De> to note that the .req file is not being created in the outbound dir.
 >
 > I believe you, but don't know why that's important here.

Because wuth the REQ file in the outbound dir, it will get sent twice. ;)

 >  De> The simplest way to do a FREQ is:
 >  De> echo filenameiwant.foo >> /sbbs/ftn/outbound/0e32000c.req
 >
 > That's not super difficult, but not as easy as "FR:filename" in the
 > subject line of a netmail, IMHO.

Ah, I had thought you were doing the manual method, not the Synchronet method using SBBSEcho.

 >  De> If you then want to force a callout:
 >  De> touch /sbbs/ftn/outbound/0e32000c.dlo
 >  De> (Or run binkit -l 1:3634/12)
 >
 > But wouldn't that just create an empty (0 byte) .dlo file which would
 > not be pointing at the .req file?  Normally a .?lo file is a text
 > listing of the actual filename/pkt/.?ut to be sent.  In this case the
 > .dlo file wouldn't have that info.

Yes, the empty .flo file is a "flow file" that causes a callout as soon as possible.

Packet files (.?ut) also do no show up in .?lo files since they trigger a callout on their own.

REQ files are special in that they're transferred during connections but *do not* trigger a callout, so to trigger a callout rather than just wait for the next time you connect, you need to create a file that does trigger a callout.  That's what a zero-length .dlo file does.
---
 þ Synchronet þ The future of BBSing

.