| View previous topic :: View next topic |
| Author |
Message |
sirloxelroy
Sentinel
Joined: Nov 16, 2006
Posts: 26
Location: BFE
|
 Posted: Mon Jan 26, 2009 9:30 am Post subject: ACLs of server not being read. :-( |
|
Well all, I have run into the problem I had with OO 3.0. THe ACL of a file is not being read. It reads the Unix permissions fine, but being we run Leopard, and Leopard defaults to 744 default write permissions we have ACLs setup to allow group aaaaa to allow custom FRWX access. Now all the files are opening as Read Only. 
Last edited by sirloxelroy on Tue Jan 27, 2009 7:44 am; edited 1 time in total |
|
| Back to top |
|
 |
sirloxelroy
Sentinel
Joined: Nov 16, 2006
Posts: 26
Location: BFE
|
| Posted: Mon Jan 26, 2009 9:37 am Post subject: HOLD for a minute, could be another problem. |
|
| Please hold on this, still doing some research, could be another problem. |
|
| Back to top |
|
|
sirloxelroy
Sentinel
Joined: Nov 16, 2006
Posts: 26
Location: BFE
|
| Posted: Mon Jan 26, 2009 9:56 am Post subject: Nope, it is not reading ACLs :-( |
|
| We are running NeoOffice 3.0 Intel with Patch 2 installed. Tested same file with IBM Symphony and it opened RW. |
|
| Back to top |
|
|
sirloxelroy
Sentinel
Joined: Nov 16, 2006
Posts: 26
Location: BFE
|
|
| Back to top |
|
|
pluby
The Architect
Joined: Jun 16, 2003
Posts: 11949
|
| Posted: Mon Jan 26, 2009 10:06 am Post subject: Re: Nope, it is not reading ACLs :-( |
|
| sirloxelroy wrote: | | We are running NeoOffice 3.0 Intel with Patch 2 installed. Tested same file with IBM Symphony and it opened RW. |
NeoOffice uses the standard Unix open() function to open files so it seems to me that invoking the open() function with write access is failing or another possibility is that file locking using the Unix fcntl function is failing.
Where are these files? Are they on a remote volume? If so, what operating system is that remote volume running on? Also, what type of file system is it (e.g. AFS, NFS, etc.)?
Patrick |
|
| Back to top |
|
|
sirloxelroy
Sentinel
Joined: Nov 16, 2006
Posts: 26
Location: BFE
|
| Posted: Mon Jan 26, 2009 10:18 am Post subject: |
|
The systems are 10.5 workstations, remote home directories, and a 10.5 server housing all these files and the home directories. Everything was working fine, the only changes were this weekend I upgraded our NeoOffice from the 2.x series to the 3.0, and added everyone to the group "staff" to try and solve a shutdown issue.
The ACLs on the file server are all set to aaaaa Custom with Full Control. The Unix Permissions are 0644 with the group being AHB_STAFF2. I tried changing the users primary group to AHB-STAFF to see if that had an affect, it did not.
Last edited by sirloxelroy on Tue Jan 27, 2009 7:43 am; edited 1 time in total |
|
| Back to top |
|
|
pluby
The Architect
Joined: Jun 16, 2003
Posts: 11949
|
| Posted: Mon Jan 26, 2009 10:20 am Post subject: Re: Nope, it is not reading ACLs :-( |
|
| pluby wrote: | | Where are these files? Are they on a remote volume? If so, what operating system is that remote volume running on? Also, what type of file system is it (e.g. AFS, NFS, etc.)? |
One more question: in the same folder as the file that you are trying to open, is there a file whose name begins with ".~lock." that matches the file that you are trying to open?
I ask because starting in OpenOffice.org 3.0, NeoOffice's underlying OpenOffice.org code creates this ".~lock." file when you open a file. If another NeoOffice 3.0 or OpenOffice.org 3.0 user tries to open the same file and this ".~lock." file is there, the second user will only be able to open the file in read-only mode.
Note that if OpenOffice.org 3.0 crashes and that user created the ".~lock." file, the lock file has to be manually deleted before anyone can open the file again with NeoOffice 3.0 or OpenOffice.org 3.0.
Let us know if the ".~lock." file is the issue. If it is, I really am considering trying to remove that new code as, quite frankly, the fact that the ".~lock." file might not get deleted makes this a flaky approach to file locking.
Patrick |
|
| Back to top |
|
|
sirloxelroy
Sentinel
Joined: Nov 16, 2006
Posts: 26
Location: BFE
|
| Posted: Mon Jan 26, 2009 10:26 am Post subject: |
|
| Tested the "staff" group by removing it from a user, it did not change the outcome. |
|
| Back to top |
|
|
sirloxelroy
Sentinel
Joined: Nov 16, 2006
Posts: 26
Location: BFE
|
| Posted: Mon Jan 26, 2009 10:27 am Post subject: |
|
| No Lock File. |
|
| Back to top |
|
|
pluby
The Architect
Joined: Jun 16, 2003
Posts: 11949
|
| Posted: Mon Jan 26, 2009 10:31 am Post subject: |
|
| sirloxelroy wrote: | | No Lock File. |
Can users in the group create new files? If not, then the ".~lock." file would still be an issue since NeoOffice's underlying OpenOffice.org 3.0 code will try to create that file if it does not exist and if that fails, the OpenOffice.org code will open the file in read-only mode.
Patrick |
|
| Back to top |
|
|
sirloxelroy
Sentinel
Joined: Nov 16, 2006
Posts: 26
Location: BFE
|
| Posted: Mon Jan 26, 2009 10:36 am Post subject: |
|
| THey can create files, and save to the same folder. |
|
| Back to top |
|
|
sirloxelroy
Sentinel
Joined: Nov 16, 2006
Posts: 26
Location: BFE
|
| Posted: Mon Jan 26, 2009 10:45 am Post subject: |
|
| Tested with NeoOffice 2.2.5 Patch 0, same user, same file, no read only issue. |
|
| Back to top |
|
|
pluby
The Architect
Joined: Jun 16, 2003
Posts: 11949
|
| Posted: Mon Jan 26, 2009 10:48 am Post subject: |
|
| sirloxelroy wrote: | | THey can create files, and save to the same folder. |
OK. To see if this problem is caused somewhere in the new code that OpenOffice.org 3.0 added - we spliced our NeoOffice 2.2.5 open() and fcntl() changes into NeoOffice 3.0 Early Access so I am trying to narrow down what changed - can you do the following?:
1. Open an existing file. After it opens in read only mode, is a ".~lock." file created in the same folder as the file?
2. Create a new empty document and save it to a new file in the remote folder. Can it be saved? If so, is a ".~lock" file created in the same folder as the saved file?
Patrick |
|
| Back to top |
|
|
sirloxelroy
Sentinel
Joined: Nov 16, 2006
Posts: 26
Location: BFE
|
| Posted: Mon Jan 26, 2009 10:53 am Post subject: |
|
| Same file opened in text edit (kinda strange) but RW. |
|
| Back to top |
|
|
pluby
The Architect
Joined: Jun 16, 2003
Posts: 11949
|
| Posted: Mon Jan 26, 2009 10:55 am Post subject: |
|
| sirloxelroy wrote: | | Same file opened in text edit (kinda strange) but RW. |
TextEdit does not do any file locking.
Patrick |
|
| Back to top |
|
|
|
