Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'This is the hard way' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
This is the hard way
Authored by: qdzlug on Jan 02, '03 04:22:11PM

Hi,

Thanks for responding - I just was looking into this a little more, and wanted to provide some clarification.

When the problem happened the permissions on the two files were 644 for both, and ownership was my account. The one thing I did not check (forgot to) was if the file was locked (in the getinfo screen from Finder).

I've been trying to recreate the problem (w/o the crashing the machine part ;> ) - I can check both the Unix permissions (via either finder or command line) and if the file is locked or not (via finder) and I don't notice a change at all from the default (644 and unlocked) when importing, playing, or burning.

You do raise a good point that should have been covered in the initial post - permissions/ownership should be checked on both files first. As an aside, have you encountered this problem where the permissions/ownership were off? I can't see why the app would need to change these.

The closest thing I can find at Apple's site is a bit that talks about the locking for a mailbox file, but I think (I don't use mail.app) that just creates a lock file in the spool directory.

Jason




[ Reply to This | # ]