I've posted this to the Cygwin list already... in case that apparent
4kiB buffer rings a bell with somebody, please give a hint on where to
look. What is lftp using to read command scripts with?
--8<---------------cut here---------------start------------->8---
There is an insidious bug that affects at least lftp on the latest
cygwin snapshot as well as the 1.7.15 release. Prepare and run an lftp
script like this:
perl -e 'foreach (1..100){' \
-e 'print "ls -r file:/", ' \
-e '(map {"$_"x10. "/"}(a..z)), "\n"}' \
> test.lftp
lftp -f test.lftp |& grep -v ls:
Observe that lftp splits the commands at a 4kiB boundary (a read
buffer?) and gives an error on the part over in the next buffer as if
the buffer boundary had been an EOL (which also means that it tried to
execute the incomplete command).
Now, the script I've shown above is harmless and in fact doesn't do
anything. I haven't been so lucky, in my case the script got cut
exactly after an
rm -r /cygdrive/c
In the past I've cursed the disk in my computer at work for being so
slow, but today I was glad that it wasn't zippy. Still, the rest of the
day I've had to clean up the damage.
Under Linux I can't get lftp 4.3.3 to misbehave in the same manner even
with much larger command lines and files, so it is either something
introduced with a newer version of lftp or unique to lftp on Cygwin.
--8<---------------cut here---------------end--------------->8---
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptations for KORG EX-800 and Poly-800MkII V0.9:
http://Synth.Stromeko.net/Downloads.html#KorgSDada
_______________________________________________
lftp mailing list
lftp@uniyar.ac.ru
http://univ.uniyar.ac.ru/mailman/listinfo/lftp
