On Wed, Aug 13, 2003 at 11:25:25AM +0200, Simon Frettloeh wrote:
> Hi!
> 
> (Amanda 2.4.2p2) I've experienced a strange behaviour of amcheck: It
> complains "permission denied" on a directory on the client, that should be
> backed up.  It's just the same directory mentioned in the disklist (with
> option "tar-fast-high"). Strange thing is, that amdump (the normal backup
> routine) doesn't seem to have any problems, backing this directory up.
> 
> To me, it seems, that amcheck does something on the client without 
> root-permissions (and get's back a permission denied error) and later on 
> amdump accesses this directory with root-rights and can straightly go on. 
> Is there a part of code in amcheck/on the client, which tries to access 
> this directory before having superuser rights?
> 
> If we chmod 711 this directory, amcheck doesn't complain any more. What's 
> going wrong?

Back in May, Joshua B-L wrote this:

> > When you run amdump, amanda runs tar via the setuid root 'runtar' wrapper.
> > During amcheck, all processes are run as the amanda user.  So, if the
> > amanda user can't cd into /home/blom, you'll get those erros.  The backup
> > will probably still work...
>
> amcheck is setuid root also -- at least on my system.
> Does it change its euid to check access?

:It's not amcheck that gets run on the clients, it's selfcheck, which isn't
:setuid root.

-- 
Jon H. LaBadie                  jon AT jgcomp DOT com
 JG Computing
 4455 Province Line Road        (609) 252-0159
 Princeton, NJ  08540-4322      (609) 683-7220 (fax)