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


Click here to return to the '10.4: One solution to a launchd-cron CPU usage issue' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.4: One solution to a launchd-cron CPU usage issue
Authored by: adrianm on Sep 15, '05 10:38:38AM

This should serve as a warning to all those people who use the Finder to explore folders that were never really meant to be explored in that way.



[ Reply to This | # ]
Finder problem?
Authored by: googoo on Sep 15, '05 12:50:01PM

I agree that there are problems that occur when you use the Finder to explore outside the normal user directories, but I think that a more desirable solution would be for Apple to fix the Finder so that it does not muck up the system files. Why should there be directories that are not meant to be explored by the Finder?

-Mark

PS. Disclaimer: I usually (but not always) use the Terminal to look at these "Finder-unfriendly" directories.



[ Reply to This | # ]
Finder problem?
Authored by: TvE on Sep 16, '05 12:17:54PM
…i think that a more desirable solution would be for Apple to fix the Finder so that it does not muck up the system files…

You're wrong: No system files were modified(!) - there was ADDED a file to a - for the Finder - invisible folder

…Why should there be directories that are not meant to be explored by the Finder?…

Why? - Beacuse you can then avoid the problem described in this thread ;-)

[ Reply to This | # ]
10.4: One solution to a launchd-cron CPU usage issue
Authored by: alan-trewartha on Sep 19, '05 09:40:17AM

i don't know for sure in tiger, but in 10.3 /var/cron and /var/cron/tabs are ROOT access only. so if you've managed to make a .DS_store file in finder then you've not only got a GUI finder session logged in as admin,but as the ROOT user!

DO NOT DO THIS. in fact, how on earth did you manage this? when you've worked that out, stop it. :-)



[ Reply to This | # ]
misusing root
Authored by: sjk on Sep 19, '05 08:04:51PM

Yeah, running Finder as root or logging in with a root GUI can have undesirable side effects, like creating .DS_Store files where they don't belong. Or unexpectedly creating other root-owned files that a non-root user will have trouble accessing (reading and/or writing) later. In general, I recommend skeptically questioning anyone who suggests logging in as root to "fix" a problem.



[ Reply to This | # ]