Hello mark,

Wednesday November 29 2017, mark lewis wrote to Torsten Bamberg:

 ml>>> that's what i was wondering... i had something the other week
 ml>>> with a huge file being placed into a filebox... binkd scanned
 ml>>> and saw the file in the box before the move was complete...
 TB>> Strange...
 TB>> Usually the file-ticer generates the flowfile for binkd after
 TB>> file
 ml> transfer
 TB>> and after generating the tic.

 TB>> What sort of fileticer do you use?

 ml> i use allfix but it wasn't involved in this... in this case, it was a
 ml> script file copying files from the central procesing area's outbound
 ml> to the individual fileboxes for those that connect here via binkp...
 ml> the file being copied was on a physically different drive than the the
 ml> fileboxes so a rename wouldn't work...

.bsy and .csy files protect BSO (bink style outbound) only, a filebox is not
protected this way. That is why one should use an atomic operation writing to a
filebox. So if the source file is on the same drive one should use move
(rename) and if the source file is on a different drive one should first copy
the file to a temporary directory of a target drive and then use move (rename).

It is true for any mailer, not only for binkd.

Michael

... node (at) f1042 (dot) ru
--- GoldED+/LNX 1.1.5-b20170303