Premissions differ question?
apple Verified ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
My iMac allways preforms a 110% so it's not really a problem or big concern, but when:
Repairing permissions for “Macintosh HD”
Determining correct file permissions.
Permissions differ on ./private/var/log/secure.log, should be -rw------- , they are -rw-r-----
Owner and group corrected on ./private/var/log/secure.log
Permissions corrected on ./private/var/log/secure.log
Permissions repair complete
The privileges have been verified or repaired on the selected volume
It the only thing that ever pops up with RP and then only once in awhile???
14 replies
Sign in or join Beachball Help to reply.
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Update:
I did find that Running Maintenance Scripts sets it to -rw-r--- and Repair Disk Permissions sets it to -rw---
I at a loss, any ideas?
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I have noticed the same. Since you have narrowed it to the maintenance scripts, have you determined which one? Since it doesn't happen all the time and I know Anacron runs my daily script daily, it may be an error in the weekly script.
It appears to be a discrepancy in the permissions in the script and the permissions specified in the Bill of Materials in the receipt located in HD/Library/Receipts. Perhaps the script is supposed to reset the permissions to do its job and neglects to set them back. Whatever, it isn't the first error in the scripts.
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
It seems to be Daily Weekly and Monthly:
The X Lab: Determining when the maintenance scripts last ran:
1. Launch Terminal, in the Macintosh HD > Applications > Utilities folder.
2. At the Terminal prompt, type the following, exactly as written:
ls -al /var/log/*.out
3. Press Return.The results are:
-rw-r--r-- 1 root wheel 472417 Jul 29 00:40 /var/log/daily.out
-rw-r--r-- 1 root wheel 11397 Jul 15 21:46 /var/log/monthly.out
-rw-r--r-- 1 root wheel 21781 Jul 29 00:48 /var/log/weekly.outOK, now I wonder which is correct?
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I think those permissions we are seeing in the Terminal are not the same ones we are discussing. My daily script ran last night at 12.48 am. I just Repaired Disk Permissions and nothing was repaired. So the daily script isn't the culprit here.
My weekly script ran 25 JUL at 8:12 am and I remember about 2 days ago I Repaired Disk Permissions and that permission needed repair. I still think it is the weekly script.
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
OK I'll agree with that because in trying to track this down, I restarted last night and 60 min's later Anacron ran the daily and weekly scripts. Of course again the premissions where changed!
Are we building a mountain here or just stumbling over a mole hill
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I'm just precipitating. You are making a large natural elevation of the earth's surface rising abruptly from the surrounding level out of a small mound of earth thrown up by a mole burrowing near the surface!
Message was edited by: David.Austin.Allen
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
*Am I* building a mountain here or just stumbling over a mole hill.
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Hello den.thed,
Actually, I hope David reads this too because it may (or may not) add to the information made available so far.
My situatioin is somewhat different but is just as puzzling:
I get the following results from RP all the time:
-------------->
We are using special permissions for the file or directory ./Library/ColorSync/Profiles/Displays. New permissions are 16893
We are using special permissions for the file or directory ./Library/ColorSync/Profiles. New permissions are 16893
Permissions differ on ./Library/ColorSync/Profiles, should be drwxrwxr-x , they are drwxrwxrwx
Owner and group corrected on ./Library/ColorSync/Profiles
Permissions corrected on ./Library/ColorSync/Profiles
We are using special permissions for the file or directory ./System/Library/We are using a special uid for the file or directory ./private/var/at/jobs. New uid is 1
User differs on ./private/var/at/jobs, should be 1, owner is 0
Owner and group corrected on ./private/var/at/jobs
Permissions corrected on ./private/var/at/jobs
We are using a special uid for the file or directory ./private/var/at/spool. New uid is 1
User differs on ./private/var/at/spool, should be 1, owner is 0
Owner and group corrected on ./private/var/at/spool
Permissions corrected on ./private/var/at/spool
The privileges have been verified or repaired on the selected volume
---------------
Notice that Color Synch/Profiles/ Displays is the most common permission needing correction.
Followed by the ./private/var/at/jobs and (I think related) ./private/var/at /spool.While I have no idea why color synch/profiles keeps appearing (over months time), I seem to get the "jobs" and "spool" results after I have quit or otherwise interrupted a print job. (USB connected Epson ink jet printer works fine tho it's 7 years old. I DO suspect that Epson's Printer Utility software is to blame somehow.)
-----
Somewhat of a footnote: yesterday I ran DiskWarrior 4 for the first time. I elected to try out the new feature, including Permissions Repair. The interesting result was that DW produced a long list of repaired permissions while Disk Utility commonly produces only the above mentioned items.BTW - off topic - This first try of DW 4 took "forever" to boot from the Alsoft CD. When I checked logs today, I saw that "DiskWarrior Daemon" apparently didn't answer the call on boot-up, but did so after another try. All I saw was the Gray Apple icon for xx minutes. But the actual rebuilding process was snappier than with v. 3.01 or 3.02.
If it means anything - I'm glad you started this thread because, as you've seen, I have my own minor mystery going on with permissions.
Regards,
macnoel - 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Hi--
I did find that Running Maintenance Scripts sets it to -rw-r--- and Repair Disk Permissions sets it to -rw---
What happens is when the weekly script runs, copies and compresses the old secure.log file, then creates a new one (i.e, rotates the logs). When it does this, the script creates a new file with the -rw-r----- permissions you're seeing.
Basically, at some point, when there was a system update, they decided to tighten up the permissions on that file. But the monthly script apparently doesn't know that yet. So, when the weekly script runs at 3:15 AM on Saturday (or if you run it with some other program), the new file's permissions get set to -rw-r-----. So repairing permissions will find it with the new permissions.
If you want, I can post a short shell script that will set the permissions that will set the permissions on the new secure.log so that you won't see that any more when you repair permissions. But I wouldn't worry about it too much.
charlie
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Hi macnoel--
What you're seeing is nothing to worry about. Periodically, Apple has changed the permissions on certain files as part of an update. Particularly, in your case, you can ignore them, as they're covered in this Apple Knowledgebase article:
http://docs.info.apple.com/article.html?artnum=107298
All the issues you're seeing appear to be just informational messages that can be ignored.
charlie
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Hi macnoel
Thanks for sharing your minor mystery, wish I had a helpful button left for you!
There is something else that I ran into, when I looked into "HD / Library / Receipts / Anacron.pkg" that David suggested above. I found that the version there was 3.1 and this Anacron version is 3.2 that when installed updated itself.
So now guess it's a waiting game to see how the next weekly script runs!
Dennis
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
But in reality, you are in the wrong place, unless you have an iMac Intel that is not represented in your profile.
You are comparing apples with oranges. You have a PowerPC eMac running Mac OS X 10.3 Panther and we have iMac Intel Core Duos running Mac OS X 10.4 Tiger for Intel. Our Macs can't even run Panther, so I have been away from it for a year and a half.
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Dennis--
So now guess it's a waiting game to see how the next weekly script runs!
But you don't have to wait until it runs on its own. You can always force it to run with this command in the Terminal:
<pre class="command">sudo periodic weekly</pre>
It's not exactly the same as if it ran at the regular time, but for this purpose it's close enough. You'd only notice the difference if you were writing scripts for periodic that relied on specific environment variables being set (which would be set if you run it in the Terminal, but aren't set when the script runs automatically).
charlie
P.S.--Make sure you find my post farther up in the thread about your permissions on secure.log...
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Awesome Charlie
That's good enough for me, thanks!
Dennis