• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Sandboxing and calling Launchctl
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Sandboxing and calling Launchctl


  • Subject: Re: Sandboxing and calling Launchctl
  • From: Mark Allan <email@hidden>
  • Date: Tue, 29 May 2012 15:42:01 +0100

For anyone following, using temporary entitlements only gets rid of two of the four errors, so I still can't make scheduling via launchd work.

sandboxd still spits out:
	launchctl(14634) deny job-creation

and Xcode/run log still gives:
	launch_msg(): Socket is not connected

Other than rolling my own scheduling and writing a helper app which runs constantly in the background, can anyone think of a way around this?

Thanks
Mark

On 29 May 2012, at 09:52, Mark Allan wrote:

> The inherited entitlements don't allow access to that file, so I'm seeing this from sandboxd in the log file:
>> launchctl(4831) deny file-read-data /private/var/db/launchd.db/com.apple.launchd.peruser.501/overrides.plist
> and
>> launchctl(4831) deny job-creation
>
> I'm also seeing this in Xcode's run log:
>> Bug: launchctl.c:2425 (25957):1: (dbfd = open(g_job_overrides_db_path, O_RDONLY | O_EXLOCK | O_CREAT, S_IRUSR | S_IWUSR)) != -1
>> launch_msg(): Socket is not connected


_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: Sandboxing and calling Launchctl
      • From: Mark Allan <email@hidden>
References: 
 >Sandboxing and calling Launchctl (From: Mark Allan <email@hidden>)

  • Prev by Date: Re: Sandboxing. WTF?
  • Next by Date: Re: Sandboxing. WTF?
  • Previous by thread: Re: Sandboxing and calling Launchctl
  • Next by thread: Re: Sandboxing and calling Launchctl
  • Index(es):
    • Date
    • Thread