On Fri, Sep 29, 2006 at 06:01:46PM -0400, Steve Newcomb wrote:
> Dear Kevin, et al.,
> 
> My bug in which Amanda created its dump-holding directory with
> permissions that made it impossible for it to write on that directory
> --- it's fixed.  The fix was to change the ownership of one or more of
> the files in /home/amanda.  I'm not sure which file ownerships made
> the difference.
> 
> Anyway, only because the Amanda maintainers might be interested, I'm
> attaching my Amanda installation script (install.sh).  Search for the
> string "### Bug:" and you will see the difference that made the
> difference.  It's curious as all get-out, and I'm wondering whether I
> ran into some security fix in the version of Linux that I'm
> running. (2.6.16, in this case).
> 

> #!/bin/bash
...
> 
> ### Bug: if the below line is: 
> ###   chown -R root.disk /home/amanda
> ### then, when Amanda creates the 
> ### the holding disk (/nobackup/AMANDASPOOL/200609...)
> ### directory for the dump, it's created with root
> ### ownership and mode 700 permissions, and Amanda
> ### can't write on it.  I have no idea why this happens. 
> ### The Amanda code says it's creating this directory
> ### with 770 permissions.  --SRN
> chown -R amanda.disk /home/amanda
> 
> chown root.disk /home/amanda/libexec/runtar
> chown root.disk /home/amanda/libexec/dumper
> chown root.disk /home/amanda/libexec/planner
> chown root.disk /home/amanda/sbin/amcheck
> chmod -R 6770 /home/amanda/libexec/* /home/amanda/sbin/*
> 


All the chown's I've used require a colon (':'),
not a period ('.') between the user and group. 

If this is an error here, there are other similar
errors elsewhere in your script.

-- 
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)