hi Christian
yes that is exactly what I was doing initially, except
1. the Account_ file has my weak auth instead of the full auth.
2 as I have already said, the remote_hosts.cfg and gui_rpc_auth.cfg files
have been customised
But it is this set up that is causing me problems, hence my thought
On 23.01.2017 22:27, trueriver wrote:
> As for the network booting machines, I already have a script running
> in the initrd that sets up the boinc directories ready for the client
> to be started. At present I give the client exactly the same files it
> gets from the post install trigger, plus an
hi Christian
thanks for your reply.
I will look at the relevant threads on the devs forum, but I don't
initially see how the scenarios you describe apply to either of my
situations.
For one thing the CLI (Debian Jessie) boxes do not have virtual network
devices, and have exactly one network
On 22.01.2017 20:24, trueriver wrote:
> I believe I am seeing hash collisions in cpid on installing the client in
> Debian and Mint. I also believe the Mint package is the unchanged Debian
> one, inherited via Ubuntu.
Hi,
there was a similar issue on the BOINC dev forums recently.
Hello,
starting with your second point, I rest assured that a patch that helps
you and does not harm or confuse others would be well received also by
Gianfranco. We just need a very simple way to phrase that you want to
present a machine as new to BOINC even though BOINC has already seen it.
I
apols if this is a double post, I am not convinced the first copy went out
OK.
--
hi thanks Steffen and Christian for your kind words.
I believe I am seeing hash collisions in cpid on installing the client in
Debian and Mint. I also believe the Mint package is the unchanged Debian
one,
