As an addendum here, i have encountered a thread where a user's Terminal doesn't startup... and the window's titlebar indicates it's stuck on the login command. That particular thread hasn't played out as yet, but i can certainly envision a situation wherein the file /usr/bin/login itself is one of the corrupted items... which will render Terminal.app unusable.

In such cases, one could employ AppleScript Editor (until a self-contained app comes along):

do shell script "/full/path/to/find_sl_damaged_files > ~/Desktop/report.txt"

...where the user will need to supply the proper "/full/path/to" part.


EDIT: hmm, or perhaps Terminal's "New Command..." menu item would still be workable (without a login shell).

Last edited by Hal Itosis; 06/28/10 01:35 AM. Reason: on second thought . . .