[simonmartin]

Hi,

Two questions:

1) *Every* time I repair permissions with Disk Utility I get:

<2002-11-28 10:15:57 +0000 - Repair of privileges has started
We are using special permissions for the file or directory ./System/Library/Filesystems/hfs.fs/hfs.util. New permissions are 33261.
2002-11-28 10:19:24 +0000 - The privileges have been repaired on the selected volume.>

Are these 'Special permissions' normal?

2) If I am running a Journaled system and things need fixing with permissions or fsck, are they taken into account by the Journaling or will they be ignored when I restart (this would be pretty silly)? Should I restart as soon as fixes are made in case I have a crash in which case the Journal will revert to the last 'Good' system?

Sorry, that's three...

Simon

[Usama's Carcase]

I think you should disable journaling, do a full permissions and diagnostics check/repair, then turn it back on. from what I recall of the kb article on journaling, you don't need to repair the drive any longer with journaling active, assuming a clean, intact file system and permissions from the get-go.

[malvolio]

The "special permissions" message is normal.
To run the fsck routine on a journaled disk or partition, you need to use the -f flag. Thus the command would be "fsck -fy".
Repairing permissions apparently will work as usual.
Certain 3rd-party programs such as Drive 10 will turn journaling off when run. Others will need you to turn it off yourself. The safest course of action is to manually disable it before running any repair program. And except for repairing permissions, I always reboot after running any repair routine. Not sure it's necessary, but I do it anyway.

[Emotionally Fragile Luke]

This is exactly why Apple makes you turn on journaling through the commmand line.