Mailing Lists: Apple Mailing Lists
Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Application does not start

Mike Fahl <email@hidden> wrote:

>[...] It turned out that the .app had been
>travelling in an oldish StuffIt archive (version 4). [...]
>
> Nov 25 11:33:09 BAD WindowServer[419]: ERROR!
> execle(/WATCHOUT_141_Mac/DatatonWATCHOUT.app/
> Contents/MacOS/JavaApplicationStub) returned, err=22

The executable in the app-bundle's Contents/MacOS/ directory must have the
executable bits set, or the app can't be launched. You can change this
with:
chmod 555 Foo.app/Content/MacOS/JavaApplicationStub

The mode-bits 555 represent all write-access disabled. I can't think of
any reason to leave pieces of an application writable in normal use. Not
even the app-bundle's sub-directories. If you support installable
plug-ins, then the plug-in sub-directory should be writable, but no others.
If writing within the app-bundles is necessary, the owner or the super-user
can temporarily enable write-access to perform some task, then disable it
again. Disabling write-access to app-bundles across the board helps
prevent accidents.

-- GG
_______________________________________________
java-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/java-dev
Be sure to read the FAQ http://developer.apple.com/java/faq/ before posting
Do not post admin requests to the list. They will be ignored.


Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.