Latest update: I think that my problem has something to do with
either the sequence of when Finder is launched and/or whether Finder
is even present. I didn't think it important to mention that the user
B account is also a kiosk style of account i.e. a custom application
is launched in place of Finder. Perhaps this is causing the problem...
Oh well... I've had to resort back to cron as my scheduled osascript
command worked just fine there. I would like to get launchd working
for me though so please keep coming through with any other ideas.
Cheers,
-C
On 28/02/2007, at 8:26 PM, Christopher Hunt wrote:
> I've just made a discovery that I think is worth sharing.
>
> Firstly I have a user that can administer the computer (user A) and
> one that can't (user B). If I issue a launchctl start from the
> command line for user A then the osascript -e <command> works! Of
> course this is not the case for user B.
>
> However if I perform a "launchd bash", load the plists and the
> perform the launchctl start (all for user B)s then all is well!
>
> I'm confused... if things work under launchd bash then why
> shouldn't they outside of that shell?
_______________________________________________
MacOSX-admin mailing list
MacOSX-admin@...
http://www.omnigroup.com/mailman/listinfo/macosx-admin
