Check the docs/INSTALL file. I'm not sure but I think the compile option
is something like
--without-server
And you just follow the client install procedure for the appropriate
inetd.conf or xinetd.conf entry.
On Wed, 29 Nov 2000, Eric Wadsworth wrote:
> I agree, this topic is largely uncovered in the documentation. I spent
> several days trying to figure out how to set things up, until I realized
> that amanda had to be installed in full on the client machines as well. I
> had incorrectly assumed that amanda used some kind of UNIX networking to
> suck the data from the client computers, but I was confused as to why I
> never had to specify any authentication to be able to access those
> computers.
>
> As for massive overkill, it only installs less than a meg of binaries on
> each client. Not too bad. Compare that with Windows bloatware, and it's
> microscopic. :)
>
> ---- Eric Wadsworth
>
> On Wed, 29 Nov 2000, Harri Haataja wrote:
>
> > On Tue, 28 Nov 2000, Randolph Cordell wrote:
> >
> > > How is installing for the clients different than for the server? That is not
> > > evident in anything I've read (README, INSTALL and the entire chapter online
> > > at www.amanda.org). Do I need to do the whole ./configure, make, make
> > > install process for each client? IT seems that's massive overkill.
> >
> > You can configure them --without-server. Otherwise, it's pretty much the
> > same.
> >
> >
> >
>
