From: Maarten LITMAATH (Maarten.Litmaath@cern.ch)
Date: Fri Mar 21 2003 - 15:04:11 EST
Dear Tru64 Managers,
as usual this list has excellent response time: first reply in 4 min!
Here is the relevant part of the example I sent earlier:
--------------------------------------------
> date > foo.txt
> date > bar.txt
> chmod 444 foo.txt
> mv foo.txt bar.txt
mv: cannot unlink foo.txt: Permission denied
--------------------------------------------
First of all, our exact version is 5.1a with PK3.
Second, the "mv" is not an alias, just /bin/mv.
Third, here is the relevant portion of the system call trace from the
"truss" command:
------------------------------------------------------------------------
stat("bar.txt", 0x000000011FFF5B58) = 0
stat("bar.txt", 0x000000011FFF5B58) = 0
stat("foo.txt", 0x000000011FFF5B58) = 0
lstat("foo.txt", 0x000000011FFF5268) = 0
lstat("bar.txt", 0x000000011FFF5128) = 0
access("bar.txt", F_OK) = 0
access("bar.txt", W_OK) = 0
access("foo.txt", W_OK) Err#13 Permission denied
------------------------------------------------------------------------
Fourth, let me already thank the people who responded so-far:
Lucien HERCAUD - confirmed bug on 5.1a PK1
Daniel Lungu
Bryan Lavelle (HP) - bug not found on 5.1a PK1, PK4
Gregg Palmer
Joe Senulis - confirmed bug on 5.1a PK3
Bob Sloane
Didier Godefroy
So we have a bit of a weird situation: at the same OS level some people
have the bug, others do not. The behavior in the example _is_ a bug,
because the absence of write permission for the source file is irrelevant
for the "mv" to succeed (and indeed, a "mv -f" works fine).
I will post a summary when a resolution has been arrived at.
Regards,
Maarten.Litmaath@cern.ch
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:13 EDT