launchd question

Christopher Hunt huntc at internode.on.net
Thu Mar 1 12:41:28 PST 2007


On 02/03/2007, at 7:00 AM, macosx-admin-request at omnigroup.com wrote:

> On 28-Feb-2007, at 16:21, Christopher Hunt wrote:
>> dev at lists.macosforge.org forum after having explained my problem:
>>> Known bug in Tiger, and fixed in Leopard.
>>> For most practical purposes, LaunchAgents don't function as
>>> advertised in Tiger.
>>> You can use them as long as you never logout.
>>
>> In other words avoid LaunchAgents for Tiger.
>
> I don't think it is at all that simple.
> Every LaunchAgent I've
> PROPERLY setup has worked just fine.
As Apple said, as long as you don't log out then all should be well.  
Do you log out?

> However, osascript ASSUMES the
> Finder is present, so without a finder it's going to be weird.
So how come then that cron works just fine for me? I have a crontab  
for the specific user - same user, same environment, same command.  
The osascript doesn't work under launchd but it does under cron.

>
> I suspect there's more to this than simply "they don't work".
I'm curious as to whether you're logging out or not. If you're not  
logging out then things might be fine for you.

Cheers,
-C


More information about the MacOSX-admin mailing list