 |
 |
Permissions repair oddity
|
|
|
|
|
Mac Enthusiast
Join Date: Mar 2002
Status:
Offline
|
|
Every now and then I'll repair disk permissions on my OSX startup volume to avoid potential problems. Every time I do it I get this message:
Permissions differ on ./usr/share/man/man3/DB.3, should be -rw-r--r-- , they are -r--r--r--
It will then claim to repair the permissions. However, if I look at the actual file in the terminal the permissions are unchanged! What gives? Is it OK for this file to have the read-only permissions? Is there any harm in manually changing the file permissions with chmod to match what Disk Utility claims they should be?
|
|
|
| |
|
|
|
|
|
|
|
Senior User
Join Date: Jan 2001
Location: Zurich, Switzerland
Status:
Offline
|
|
Every time I do it I get the following...
We are using special permissions for the file or directory ./System/Library/Filesystems/hfs.fs/hfs.util. New permissions are 33261
|
|
|
| |
|
|
|
|
|
|
|
Professional Poster
Join Date: Apr 1999
Location: Copenhagen, Denmark
Status:
Offline
|
|
|
|
|
JLL
- My opinions may have changed, but not the fact that I am right.
|
| |
|
|
|
|
|
|
|
Junior Member
Join Date: Dec 2001
Location: My own personal purgatory
Status:
Offline
|
|
Originally posted by Boochie:
Permissions differ on ./usr/share/man/man3/DB.3, should be -rw-r--r-- , they are -r--r--r--
Whenever I've run permissions repair, the line immediately after this that shows up is "Permissions differ on ./usr/share/man/man3/db.3, should be -r--r--r-- , they are -rw-r--r--" - note db.3 versus DB.3 . Given that the HFS(+) disk format is case-insensitive, these two are in fact the same file, so the repair is just toggling back and forth between the two states, leaving it in the state it was originally.
Why this actually happens, I dunno. 
|
|
"A scientist can discover a new star but he cannot make one. He would have to ask an engineer to do it for him."
|
| |
|
|
|
|
|
|
|
Mac Enthusiast
Join Date: Mar 2002
Status:
Offline
|
|
I had forgotten that files are case-insensitive in HFS+, thanks for the reminder. I also see the same message going in the other direction for db.3. Presumably it's a bug in the the permissions repair routines, but it does make you wonder which state is correct. Most of the files in that directory are read-only, so perhaps that's what db.3 should be as well.
Originally posted by Glennfield:
Given that the HFS(+) disk format is case-insensitive, these two are in fact the same file, so the repair is just toggling back and forth between the two states, leaving it in the state it was originally.
Why this actually happens, I dunno. [/B]
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
 
|
|
|
Forum Rules
|
|
|
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
|
HTML code is Off
|
|
|
|
|
|
|
|
|
|
|
|
|
Top
