If anyone is still interested, I bundled up an Automator action that will allow you to set display profiles from custom workflows inside my ProfileMenu application.
launchd does not give you a full shell environment, so if any part of your script is dependent on any particular user’s environment variables, they need to be set in the job itself.
Don’t write a login hook if you actually want your code to work in the future, and don’t expect launchd to expand tildes or provide a full login shell environment anytime soon. There are plenty of ways to determine the user’s name and build the correct path yourself.
A profile built for one display/video card combination will not be valid on another, even if they’re the same make and model. You need to calibrate every workstation individually for there to be any point to calibrating them at all, otherwise you’re just substituting one inaccurate generic profile for another inaccurate generic profile, which isn’t going to make soft-proofing any easier for anyone.
The actual setting of the profile used to be recorded in /Library/Preferences/.GlobalPreferences.plist I believe, but I’m not seeing it there now. Either way, that preference is keyed by a unique device ID which will also not translate from one machine to another, so simply duplicating this file would not help. You could write a small tool to set the profile for you on login, or I have an application that lets you choose the profile from the menu bar.
I don’t really understand what it is that you’re asking, but “.no” is a perfectly valid top level domain for the country of Norway, so odds are good someone other than you is providing authoritative responses to such lookups.
I have no idea what anyone would need 80 iPods for, but is your server box the one doling out the DHCP functionality or are you using a router for this? If it’s a router, is it smart enough to make decisions based on MAC addresses?
I don’t want to use VPN tracker as I try to minimise the use of 3rd party software wherever possible, and like to keep things as simple as possible for my clients…[/p][/QUOTE]
I can certainly appreciate the desire to minimize dependencies, but in this case, you’ve already introduced a 3rd party, and there is very little chance that any of Apple’s testing matrices are going to place McAffee compatibility at a very high priority at any point in the near future. At the very least, [i]trying[/i] a different client would tell you whether the issue you’re facing is more likely to be an Apple or a McAffee problem, regardless of whether or not you decide to deploy it as a permanent solution.
[QUOTE]Under 10.6, I can see in the Network preferences that the VPN network interface has received the correct DNS server as it’s listed in grey, however the machine simply will not use it.[/p][/QUOTE]
If the +trace option of dig confirms this, then I’d say try another client like VPNTracker.
Recent Comments