On Wednesday 13 July 2005 17:07, Vicki Stanfield wrote:
>Gene Heskett wrote:
>>On Wednesday 13 July 2005 14:22, Jon LaBadie wrote:
>>>On Wed, Jul 13, 2005 at 12:22:56PM -0500, Vicki Stanfield wrote:
>>>>Jon LaBadie wrote:
>>>>>On Wed, Jul 13, 2005 at 10:05:29AM -0500, Vicki Stanfield wrote:
>>>>>>I have set up a client for amanda to backup. The amanda server
>>>>>>runs as user backup, so I set up the client to be run by backup
>>>>>>as well. I am getting errors in my amanda main report:
>>>>>>
>>>>>>moe        /tmp/rt3.backup lev 0 FAILED [disk /tmp/rt3.backup,
>>>>>>all estimate failed]
>>>>>>
>>>>>>
>>>>>>In the sendsize log I see the following line:
>>>>>>
>>>>>>runtar: error [must be invoked by amanda]
>>>>>
>>>>>Looks like the executable was compiled with the default amanda
>>>>>user, "amanda".
>>>>>Thus, it expects to be run only by a user named amanda.
>>>>>
>>>>>After compile you decided to name the amanda user "backup".
>>>>>The excutables on the client must be compiled to know of this.
>>>>>
>>>>> configure --with-?user?=backup ...
>>>>>
>>>>>(Not certain of the exact "with" option).
>>>>
>>>>Actually I just used yum to install the amanda-client, so there
>>>>was no compiling involved. So I assume that I need to use a
>>>>tarball if the username is not amanda, then?
>>>
>>>Don't know yum.
>>
>>Yellowdog Updater, Modified.  It can keep your system uptodate
>>automaticly if you run it daily AND your distro supports it.
>>
>>But, he has just ran into one of the main reasons we always
>> recommend building amanda from the tarball, that way you don't get
>> stuck with somebody elses grand view of the ideal preferences.
>>
>>Or he could just add a user named amanda, and make that amanda a
>>member of the group disk or backup.  Putting the execute daily
>> stuff into the user amanda's crontab by becomeing amanda and doing
>> a crontab -e to add it.  That _should_ work if he is not
>> comfortable working with the compiler.
>>
>>>Do some of those pre-built packages have a way of specifying
>>>local preferences?  Or is that only with the source packages.
>
>But the problem there is that I inherited a working amanda server
>configuration which runs as backup. I would have to change all the
>exsting clients and the server to make them run as amanda, right? I
> can do the tarball thing. No problem. I just wanted to make sure
> that that was the only option.
>
>Vicki

Running the server as 'backup' isn't a no-no if it was built that way, 
and apparently it was.  OTOH, with a good config script, the build & 
install of the new versions won't be over 15 minutes per machine 
thats got some real, today ability.  Assuming of course the compiler 
is installed on the clients.  Some remove it as a security risk of no 
little importance.

Lets get something out of the way here, what versions are installed 
and running, Vicki?

That said, most client builds are backwards compatible with older 
servers.  And, I see no reason why the clients cannot run as a 
different user than the server runs as, as long as the .amandahosts 
file on each client is current & uptodate.  I can't think of a reason 
the various clients cannot run as a nearly random, unpriviledged 
user, can you Jon or Stephen?

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.35% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2005 by Maurice Eugene Heskett, all rights reserved.