On 1/9/14 5:13 PM +0900, Daniel wrote:
On 9/01/2014 2:47 AM, Rob wrote:
Daniel <[email protected]> wrote:
It no longer removes the parent.lock file!
Please read it again.
The file is not removed, only the lock on it is released.
The file itself remains, and this is OK.
So what does this mean?? Is SeaMonkey altering the properties of a file
(i.e. Read Only or not) without any intervention by me??
Did I write that?
No, I did not.
Nor did I say that you did!
As this is the second time that you post without reading
Read each time!! May not have understood what you have typed, but I have
read.
what
is written and/or researching what it means, I choose to not
further elaborate on the matter.
Sorry, Rob, I am reading what you type ... and I'm trying to interpret
that, which, when I read "The file is not removed, only the lock on it
is released" to me, that is suggesting that the condition of the file
"Read" property is being altered.
Or is the contents of the file (on my Hard Drive) being altered, or .....?
Just trying to improve my understanding!
I think what Rob is trying to explain is that older versions used the
file as a kind of static semaphore, where its presence indicated the
lock state and its deletion indicated that things were loosy-goosy. (He
may not have chosen that term.) Newer versions, on the other hand, seem
to just place an actual lock on the file itself, while the file's
presence stays static. The lock comes and goes while the file does not.
As a tech demigod, he shan't elaborate further. His frustration trumps
your understanding (or lack thereof).
--
/////////////////////////////////////////////////////////
// Trane Francks [email protected] Tokyo, Japan
// Practice random kindness and senseless acts of beauty.
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
