On Monday 27 March 2006 12:16, Grant wrote:
So you're saying if I don't use PKI, the remote system is going to
prompt me for a password after I'm already logged in? You say each
compile that goes to an ssh host will ask for a password. At what
point in the emerge process does this happen?
It's probably better to use distcc over ssh, using an ssh-agent
and PKI authentication.
How would ssh and PKI be set up in
the workflow? It isn't mentioned here:
http://www.gentoo.org/doc/en/distcc.xml
1) On the server, set up the shell account that will use distcc via
Is there anything wrong with
making a remote machine [a] distcc system?
Not really, but you do need to realize that distcc doesn't guarantee
that jobs will be sent to the remote machines and will not prevent
jobs from being run locally.
Good to know for sure.
I was kinda
On Friday 24 March 2006 13:25, Grant [EMAIL PROTECTED] wrote about
'Re: [gentoo-user] Hosted server as distcc machine':
It's probably better to use distcc over ssh, using an ssh-agent
and PKI authentication.
How would ssh and PKI be set up in
the workflow? It isn't mentioned here
On Wednesday 22 March 2006 17:10, Grant [EMAIL PROTECTED] wrote about
'Re: [gentoo-user] Hosted server as distcc machine':
Is there anything wrong with
making a remote machine [a] distcc system?
Not really, but you do need to realize that distcc doesn't guarantee
that jobs
Is there anything wrong with
making a remote machine [a] distcc system?
Not really, but you do need to realize that distcc doesn't guarantee that
jobs will be sent to the remote machines and will not prevent jobs from
being run locally. If there are not enough distcc hosts to support the
On Monday 20 March 2006 22:25, Grant [EMAIL PROTECTED] wrote about
'[gentoo-user] Hosted server as distcc machine':
Is there anything wrong with
making a remote machine [a] distcc system?
Not really, but you do need to realize that distcc doesn't guarantee that
jobs will be sent to the remote
7 matches
Mail list logo
