code.edbaskerville.com

As it turns out, the privilege failure mentioned in the last post was not being reported by the calls to xgridctl to start and stop the controller, but rather the ones that were trying to simply get what the current status was. In Leopard, you always need to run xgridctl as root, even just to get status.

However, when I recoded the status-getting code to use the privileged tool to do its work, it’s reporting that the controller is off when doing xgridctl c status at the command line reports that it’s running. One more roadblock, but this should be the last one. Given how my weeks go, it probably won’t be until next weekend (a long one, fall break).

To those who have been requesting that XgridLite start working on Leopard: first of all, sorry it’s taken so long for me to think about it. I didn’t even upgrade myself to Leopard until the middle of this year, and since then I’ve been pretty busy working, touring with my band, and finally starting a new life as an ecology grad student. The good news is that being a grad student means I’ll be running simulations again soon, so I’m selfishly motivated to have a working XgridLite on my machine.

I finally popped open the code after a long hiatus and tried it out. I was hoping the problem would just be a simple problem like the controller argument syntax changed, but I got this message in the console log:

ERROR: you must be running with root privileges

This is the same message you get when you run xgridctl c start as a regular user from the command line. So the mechanism I used to run as root under Tiger is clearly not working under Leopard. Perhaps this is related to the new security mechanisms (which I know nothing about) that Apple added.

I’ll try to tackle this tomorrow.