Separate names with a comma.
Discussion in 'Distributed Computing' started by Spoooon, Jul 3, 2000.
Like the title says.
What is it and who are they?
Actually, I meant as a service. That's what I get for trying to type one thing and talking to someone else about another.
When the client runs as a "service" it means that it is started during boot-up, regardless of whether anyone logs onto the computer (if you pause for logon, that it).
You can't forget it, you have trouble even stopping it.
To install it as a service, at a command prompt in the proper DNET folder, just type dnetc.exe -install and it will tell you that you have installed it as a service.
But, it is not running until your next reboot, or until you start it manually with just "dnetc.exe"
There is no performance benefit, just a "set and forget" kind of thing. See some other threads about how to manage the client when it running as a service.
Does anyone know if it will still fetch / flush to the keyservers/pproxies or to remote buffers on a network if the PC is not logged in?
It will flush to the keyserver (d.net, Mika, or whatever else is specified) and will use remote buffers AS LONG AS it has permissions to access the remote directory. If the client is running on a Win9X machine and the remote drive is shared with a password or on an NT machine it probably won't. However if the client is running on an NT machine, you can choose a username and password that the Distributed.net client service will run under. That would allow it to access the remote directory.
What they really mean is to make sure that the DNETC.ini file reads "Russ@compucheap.com" -
That will fix everything....