I've installed boinc on multiple win2k machines configured for multiple users. I install the cli using boinc_cli -install, and find it running after restarting my computers. However, after I log off, the program quits, and doesn't restart. How can I get it to continue running regardless of who logs in or out? I don't have admin rights or access to regedit.

Seti classic was able to do this; I used an autoinstaller from http://tools.komlenic.com/144

I've not tried this, but heard that it seems to be a common problem...

Seems the windows boinc_cli is buggy when it comes to services...

hmmm....

same "problem" here...(BOINC 3.19)
i've installed the BOINC service on several w2k servers,
however, the service terminates only when i logon, "NET START BOINC"
and then logoff from the console.
doing the same in an RDP session doesn't terminate the BOINC service.

very strange ;)

Best Bytes®,
Harry

I use WinXP but it should function basically the same. When I installed it as a service, and then told the service to startup, it told me that it started up and then immediately ended for some reason. So in trying to figure out the cause, I found that for some reason it installed the BOINC service to run with some specific creditials instead of using system credentials. I don't remember what they were, just that they had "network" in the description/name. I don't know why BOINC does this, but changing it to system fixed that problem.

So how does this relate to your problem? Setting a service to use system credentials causes the service to start up with Windows and is not affected by users logging on or off of the computer. I don't remember how much control Win2k gives you over services, but if the "allow to interact with desktop" checkbox is there, make sure it is clear. That insures that it remains hidden as a background task (it will show up in task manager however). Again, I don't know why BOINC doesn't just set itself. Now a bit of a disclaimer. The very fact that you were able to install BOINC as a service without any administrative or registry privelidges is promising. But, you may not be able to set it to run with those credentials without more privelidge than you have. If not, you *may* be able to set it to run with your credentials. I don't think the BOINC Cli version has any visible attributes to it, but if it does, using your personal credentials will not hide the service.

But again, without administrative privelidge, you may or may not be able to do any of it. On the XP machines at my school, I had "Power User" privelidge on some of the machines and was not allowed to create or modify services, but I could view them both in the registry and the Service viewer. My work computer though, I'm not exactly sure what my user status is, but while I don't think that it is really administrative, I seem to have complete control over my computer and can modify/add services to my heart's content. So, in short, if you can modify services, great. If you can't, I don't think there is really anything you can do short of hacking the computer's administrative account. But I don't think your work would appreciate that. :)

Chris

> I use WinXP but it should function basically the same. When I installed it as
> a service, and then told the service to startup, it told me that it started up
> and then immediately ended for some reason. So in trying to figure out the
> cause, I found that for some reason it installed the BOINC service to run with
> some specific creditials instead of using system credentials. I don't remember
> what they were, just that they had "network" in the description/name. I don't
> know why BOINC does this, but changing it to system fixed that problem.
>
> So how does this relate to your problem? Setting a service to use system
> credentials causes the service to start up with Windows and is not affected by
> users logging on or off of the computer. I don't remember how much control
> Win2k gives you over services, but if the "allow to interact with desktop"
> checkbox is there, make sure it is clear. That insures that it remains hidden
> as a background task (it will show up in task manager however). Again, I don't
> know why BOINC doesn't just set itself. Now a bit of a disclaimer. The very
> fact that you were able to install BOINC as a service without any
> administrative or registry privelidges is promising. But, you may not be able
> to set it to run with those credentials without more privelidge than you have.
> If not, you *may* be able to set it to run with your credentials. I don't
> think the BOINC Cli version has any visible attributes to it, but if it does,
> using your personal credentials will not hide the service.
>
> But again, without administrative privelidge, you may or may not be able to do
> any of it. On the XP machines at my school, I had "Power User" privelidge on
> some of the machines and was not allowed to create or modify services, but I
> could view them both in the registry and the Service viewer. My work computer
> though, I'm not exactly sure what my user status is, but while I don't think
> that it is really administrative, I seem to have complete control over my
> computer and can modify/add services to my heart's content. So, in short, if
> you can modify services, great. If you can't, I don't think there is really
> anything you can do short of hacking the computer's administrative account.
> But I don't think your work would appreciate that. :)
>
> Chris
>
>

Without admin rights, I haven't been able to set it to system credentials.

But I think I've figured out a way around: using www.firedaemon.com.

Thanks,
Rameen