🚀 go-pugleaf

The last time I used CMS it had the weird property that if I took a
snapshot of the files owned by user X (because he had a file I wanted
to read or something), then user X edited that file by reading it, changing
it, then writing it (with the same name but in a new disk location),
MY access of that file would bomb out.  The reason for this bomb out was
that my pointer to his file was still pointing to disk location where the
old file was located, not to the updated copy.  Has this been fixed?
If not, how do people deal with this strange property on a day-to-day basis.

George Otto
Bell Labs, Indian Hill
----------------------