Has anyone had any luck with using the local system account when running BOINC as a service?
I find the service runs but I get no connectivity:

5/05/2005 6:32:23 p.m.|SETI@home|Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
5/05/2005 6:32:44 p.m.|SETI@home|Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
5/05/2005 6:32:44 p.m.|SETI@home|No schedulers responded
5/05/2005 6:32:44 p.m.|SETI@home|Deferring communication with project for 1 minutes and 0 seconds
5/05/2005 6:33:44 p.m.|SETI@home|Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
5/05/2005 6:34:05 p.m.|SETI@home|Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
5/05/2005 6:34:05 p.m.|SETI@home|No schedulers responded
5/05/2005 6:34:05 p.m.|SETI@home|Deferring communication with project for 1 minutes and 0 seconds

---

Cheers

Gav



Nothing is 'fool-proof', someone will always invent a better fool!

I havn't had any unsual problems running this way. It did get stuck in a RPC recently, but a restart cleared it out.

---

BOINC WIKI

BOINCing since 2002/12/8

I've not had a problem with this either Archon. Running the CLI as a service has actually been much smoother than using the GUI to start it. I have mine setup to logon to Local System account, and also i've checked the box for "allow service to interact with desktop" although to be honest I have no idea what that does. LOL.

Hope you get it sorted out.

Dig

---