Is the OS-X BOINC client able to run as a system process on bootup, and not merely a user process engaged once a user is logged in? We have over 100 OS-X clients in a managed client environment, and they spend most of their time at the login screen. Are project workunits downloaded and processed and held with the computer or the user? How can we ensure that computers at the login screen are also BOINCing away?

To extend the question just a bit: Does the crontab solution work the same as with the classic S@H CLI version? Specifically, does the OS X CLI gracefully handle being called when it's already running?

The answer is Yes, but I haven't done it. I'm using my government work computer, and I'm just a bit hesitant about installing stuff on it that isn't official. Geoff R. responded to my question about this a few months ago, and sent me an email with the details. Drop me an email note at beadman@mac.com and I'll forward the info to you.

C

---

Join Team MacNN

> To extend the question just a bit: Does the crontab solution work the same as
> with the classic S@H CLI version? Specifically, does the OS X CLI gracefully
> handle being called when it's already running?

Yes: if you do it in an active terminal window, you see this,

2005-01-10 12:22:06 [---] Another instance of BOINC is running

and no new version starts. I've had boinc work with a crontab attempting to launch it every 10 minutes, and that's fine.

---