Subj : Re: Adding kermit as a protocol option
To : Christian Sacks
From : Alexander Grotewohl
Date : Tue Aug 08 2023 02:09 pm
On 08 Aug 2023, Christian Sacks said the following...
CS> I've installed `gkermit` on my linux host, and in protocol editor have
CS> made a new "kermit" protocol, and the send/recv commands are like this;
CS>
CS> Send Command � /usr/bin/gkermit -d /tmp/kermit-send.log -Ts %3
CS> Recv Command � /usr/bin/gkermit -d /tmp/kermit-recv.log -Tr %3
CS>
CS> With %3 as the filename(s), it seems to generate a file.lst on the
CS> client end, and inside the file that it downloads just has a line for
CS> each file with it's full filepath on the bbs, and doesn't download the
CS> actual file...
having searched around the docs a bit it looks like kermit does batch xfers differently than most bbs software would expect. you would likely just have to turn 'batch' off in the protocol config and have it work one file at a time. (batch toggles whether %3 is just one file by itself, or a file list file)
CS> I looked at the default sexyz config which uses @%3 which I thought
CS> might be required instead, but adding the @%3 instead just errors
CS> immediately with the filename not being found according to the client.
@ is a sexyz parameter not a mystic one. if it finds that @ at the beginning of the filename it will read that file line by line and send each of the files listed. kermit doesn't support this so that's the problem.
if you're comfortable doing a little programming you could probably make a
script to read the lines in file.lst then run gkermit like it wants:
