There seems to be an issue with the InterprocessLock on OSX (in the juce master branch, but I didn’t find any thread that suggest this is fixed in modules).
Isn’t the idea that the /var/tmp/juceAppLock_* files are supposed to be deleted when the application shuts down? It seems that (on OSX 10.6.8 ) those files never get deleted. This doesn’t result in any problems when you are only using a single user account. Even those applications that allow only one instance (by overriding JUCEApplication::moreThanOneInstanceAllowed) work fine.
However, when you try to start a standalone juce application that has the single instance limitation enabled with different user account, it will exit immediately and silently for the second user, since (s)he does not have write permissions to the lock file.
Is this a known issue, already fixed in the modules branch? Or is there anything we could and have to do to fix this in our application code?