Hi Oli,

On 2021-09-15 14:41:18, you wrote to me:

 Ol>>> How is that different to arcmail bundles referenced in a FLO file?

 WvV>> Access to files in a regular BSO directory is strictly regulated
 WvV>> through the use of lock files (*.csy, *.bsy). So different programs
 WvV>> won't access the same files at the same time. There is no such
 WvV>> standard for fileboxes.

 Ol> True, no formal standard. But it's obvious that the program should lock the
 Ol> file before modifying it or when a transfer is in progress. No idea how
 Ol> binkd and hpt handles fileboxes though. I safe strategy would be to lock
 Ol> all files in a filebox when a session starts

It's not safe. As you show in the wikipedia quotes on file locking, it's cooperative on unix-like os's.

 Ol> (at the same time the *.bsy file is written).

There are no *.bsy files written in fileboxes.

 Ol> As fileboxes usually don't replace BSO, but working in addition to
 Ol> BSO, the program modifying anything in the filebox can create a .bsy
 Ol> file in the BSO.

It could, but it doesn't accomplish anything, because they will be ignored by other processes accessing the filebox.

 Ol> Of course we cannot rely on such behaviour, because there is no
 Ol> standard.

Indeed. So don't rely on it, period.

 Ol> But from the tossers perspective it shouldn't be a problem to safely
 Ol> create / modify 'dailyBundles' in fileboxes. Just create a *.bsy file.

And that wouldn't help at all, when those *.bsy files are ignored by other processes accessing the filebox...


Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815