codeslinger wrote:
> Hi John,
>
> Thank you very much for the info. I learn something new every day, did
> not know that about POSIX. Dealing with all these different file
> systems must be quite a challenge.
>
> if one were to use something unique for the extension such as
> '.@rename.[pid]' instead of a generic '.tmp' then automatic file
> recovery could be possible.
>
We do use a unique identifier. I was just using .tmp as a simple
example. We actually use something like .pid.randomnumber.tmp
So we are safe to recover as long as the connection is still alive. The
problem is that if we lose the connection, another process would have to
search/guess what the correct old value was.
John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
codeslinger wrote:
> Hi John,
>
> Thank you very much for the info. I learn something new every day, did
> not know that about POSIX. Dealing with all these different file
> systems must be quite a challenge.
>
> if one were to use something unique for the extension such as
> '.@rename.[pid]' instead of a generic '.tmp' then automatic file
> recovery could be possible.
>
We do use a unique identifier. I was just using .tmp as a simple er.tmp
example. We actually use something like .pid.randomnumb
So we are safe to recover as long as the connection is still alive. The
problem is that if we lose the connection, another process would have to
search/guess what the correct old value was.
John
=:->
-----BEGIN PGP SIGNATURE----- enigmail. mozdev. org
BCYSNAAMRApcuAJ 98slgh1MsOlHqHv eDFmTbNoLJp3ACg v1zf UEwLsLTk=
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://
iD8DBQFHkSYQJde
YHOYF2N4Km15GYV
=bKMZ
-----END PGP SIGNATURE-----