On Sep 3, 2009, at 11:02 AM, Damien Sorresso wrote:
On Sep 3, 2009, at 10:37 AM, Dean Shavit wrote:
I am aware of that. But there's differences in behavior. In Leopard, specifying any Session Type listed in the LaunchAgent using "sudo" worked to write the Disable key in the plist targeted. In Snow Leopard, this behavior does not hold true for the overrides.plist
I'd argue that the Leopard behavior was improper. Asking to modify a job in a session where it cannot exist should be a no-op.
In any case, we really hope to clean up the mess of sessions post- Snow Leopard. We also just want to get rid of the Disabled key entirely.
Well, not get rid of it, but we certainly want to change the behavior behind it. So we may keep the name of the key, but it would act differently. -- Damien Sorresso BSD Engineering Apple Inc.