site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com On Aug 4, 2006, at 2:25 PM, Kevin Brock wrote: On Aug 4, 2006, at 2:20 PM, Dave Zarzycki wrote: On Aug 4, 2006, at 1:58 PM, Peter Bierman wrote: That is odd. Can you show me your plist? davez _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... My first guess would be the umask. For that to be involved, you might be creating the socket from a script instead of as part of your package payload. Either have your application create the socket at runtime and assign correct permissions then, or make the socket part of your package payload. Agreed. Although as the launchd maintainer, I'd rather see the socket created as a part of the launchd job schema outlined in the property list, but that is my personal agenda. :-P The socket is not created by the installer. The socket is created by launchd when launchd runs, using a launchd schema, and if I stop and restart launchd I can see it set the permissions back to 755 each time on the affected systems, even though the permissions in the launchd .plist say that the socket should be 777. If it's a umask problem it would have to be a umask for launchd in general, and I'd expect that to break all *kinds* of things. This email sent to site_archiver@lists.apple.com