Bug 796 - Cannot unset read-only folder attribute via Windows XP
Cannot unset read-only folder attribute via Windows XP
Status: RESOLVED WONTFIX
Product: Samba 2.2
Classification: Unclassified
Component: File Services
2.2.8a
All Windows XP
: P3 major
: ---
Assigned To: Gerald (Jerry) Carter
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2003-11-20 08:13 UTC by Marco De Vitis
Modified: 2005-11-14 09:28 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marco De Vitis 2003-11-20 08:13:16 UTC
I have Samba 2.2.8a running on Mandrake Linux 9.0, in a LAN where I have some 
Win2000 Pro clients and one WinXP Pro client. Samba acts as file server and PDC.
In a share I have some directories which are set to read-only by a script on 
the Linux side, but any user can open up the folder properties on the Windows 
client and remove the read-only attribute; this is ok, it's what I want, and 
works perfectly on Win2000 clients.
On the WinXP client, instead, when opening the properties window the checkmark 
near the read-only attribute is shown in grey; if the user removes it and 
clicks on OK nothing happens, the attribute is not changed. The same user, when 
accessing to the share using a Win2000 client, has no problems.

Setting and unsetting the read-only attribute on files works fine, also on 
WinXP. Setting it on directories does not work, if I recall correctly, neither 
on Win2000 nor on WinXP. But UNSETTING it on directories works fine on Win2000, 
while it doesn't work on WinXP.
Comment 1 Marco De Vitis 2004-02-03 15:41:35 UTC
I'm not sure anymore that Samba has anything to do with this behaviour: I found
two articles on Microsoft's knowledge base stating that the readonly attribute
is totally ignored for folders, as it only indicates if the folder view has been
customized.
So, the strange thing to understand now becomes: how is it that it works fine on
Win2000? :)
Comment 2 Gerald (Jerry) Carter 2004-02-17 08:56:02 UTC
Sorry, but the 2.2 is not under development any longer.
If you can reproduce this bug against the latest 3.0 release, 
please reopen this bug and change the version in the report.
Thanks.
Comment 3 Gerald (Jerry) Carter 2005-11-14 09:28:43 UTC
database cleanup