Re: Probs with "BetterAuthorizationSample"-code
Re: Probs with "BetterAuthorizationSample"-code
- Subject: Re: Probs with "BetterAuthorizationSample"-code
- From: "Frank W. Tag" <email@hidden>
- Date: Sat, 17 Oct 2009 16:54:54 +0200
(Due to a misconfiguration I did send this message more than once -
sorry for that to all)
Hi there,
thanks to your and esp. Todds hints everything works quiet fine now.
Two additional detail question remain:
1- How can I set up the BAS to proceed an install process without the
HelperTool called necessarily at this time? While this the admin
credentials should be asked once.
2- How can I adjust the credentials life time to endless so after the
install process they would not be asked anymore? To understand this
let me explain what I am doing: My helper tool calls a kext written by
myself which provides certain system calls (in better words: it fakes
an USB HID). But from time to time the login prompt is presented,
obviously after a certain time out, and that is not what I want to see
because it disturbs the HID command processing.
Thanks a lot again!
Frank
Am 04.10.2009 um 05:37 schrieb Todd Heberlein:
1. How can I debug my HelperTool? Obviously any breakpoints set in
XCode won't work because the HelperTool is launched outside by the
launchd.
2. My idea is to use asl to debug "barefoot". But for that I have
to install aeach time when I have compiled a modified version of
the HelperTool to the system. But how to do this? InstallerTool
does not do this itself.
I have used asl_log() messages as a substitute for printf(). The
messages goes to your Console (the one under /Applications/
Utilities) and not to the "Console" in Xcode, so make sure you are
looking in the right place for output.
I think printf() will just cause the HelperTool to exit with error.
Every time I modify any code used by my helper tool I run
$ ./SampleUninstall.sh
I just had to change all the references in the shell script to my
application's Identifier. For example, my modified shell script has
the lines:
sudo launchctl unload -w /Library/LaunchDaemons/
com.netsq.ACManager.plist
sudo rm /Library/LaunchDaemons/com.netsq.ACManager.plist
sudo rm /Library/PrivilegedHelperTools/com.netsq.ACManager
sudo rm /var/run/com.netsq.ACManager.socket
And the Cocoa app's "Identifier" in the target's property window is:
com.netsq.${PRODUCT_NAME:rfc1034identifier}
(the Project is called ACManager) so "com.netsq.ACManager" is
inserted in all the appropriate places in the script.
If things are really screwed up, you can look in the directories
identified in the shell script, remove the appropriate files by
hand, and then logout and log back in (if that doesn't solve your
launchctl errors you may need to reboot as a crude but effective
step).
But once you have your SampleUninstall.sh script set up correctly,
running it each time you make code modifications should work.
Todd
--
Frank W. Tag
Dahlenhöhe 3
21077 Hamburg
Tel. (040) 432 774 11
Fax (040) 432 774 15
mobil (0160) 973 40 131
mailto:email@hidden
_______________________________________________
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