On Wed, 2003-02-12 at 10:49, Pete Poggione wrote:
> You and I are thinking the same. As I looked further it seems for some
> reason the target was not owned by root but rather by me.(?) changing
> the ownership to root eliminated all permission issues. It is now like
> this:
> 
> [root@ruby dev]# ls -l sg2
> lr-xr-xr-x    1 root     root           36 Feb 10 13:45 /dev/sg2 ->
> scsi/host0/bus0/target5/lun1/generic
> 
> [root@ruby lun1]# ls -l
> total 0
> crw-rw----    1 root     root      21,   2 Dec 31  1969 generic

Well, the mod date seems weird, in that it is set to the UNIX epoch, but
I guess that doesn't really matter.  It still doesn't appear that
amanda's group 'disk' would have access to this file, but that may be an
affect of your particular system (what OS is this?).  Your success with
mtx below means that for whatever reason, the permissions seem to be OK.

> mtx now responds correctly for user 'amanda'
> 
> [root@ruby amanda-2.4.3]# su amanda -c "mtx status"
>   Storage Changer /dev/changer:1 Drives, 6 Slots ( 0 Import/Export )
> Data Transfer Element 0:Full (Storage Element 1 Loaded)
>       Storage Element 1:Empty
>       Storage Element 2:Full 
>       Storage Element 3:Full 
>       Storage Element 4:Full 
>       Storage Element 5:Full 
>       Storage Element 6:Full 
> 
> Do you see anything weird about this or am I correct in assuming this
> should be ok?

This does indeed look like mtx succeeded.  The next step would be to
ensure that amanda can execute the changer functions via her generic
commands, like 'eject' or 'slot X'.  Something like

# su amanda -c amtape <config> slot 1

If that works, then you're all set.

Cheers,
Eric