John,
For reasons that I don't understand, predating my time at this site,
the Sun systems use "bin" for amanda user and the SGI systems use
"root" for amanda user.
Rather than allow enhanced root access via NFS I selected an equally
questionable solution, chmod o+x on the executable.
# df worked, initially # file failed but now works. Oddly enough I
didn't see any errors when trying to (manually) execute the program
from the client (with no parameters, not quite certain of the behaviour
but thought I'd see some type of access failure).
[sylt] /usr/local/libexec 3> file rundump
rundump:
Cannot read rundump: Permission denied
Its be great is either amcheck or some other post installation
utility actually ran all these checks prior to a full-live run.
Don't mean to be critical, don't know how we'd function without
Amanda, its a wonderful tool, just that there are so many possible
ways a distributed program like this can fail that cataloging and
testing for these things would be a very valuable addition.
I think we probably have it licked now, will flag you tomorrow if
I run into something else I don't understand.
thanks very much,
Brian
> >As far as the other two clients sendsize.20010628122106.debug shows
> >(the errors are the same on both clients).
> >...
> >cannot execute /usr/local/libexec/killpgrp: Exec format error
> >cannot execute /usr/local/libexec/killpgrp: Exec format error
> >sendsize: exec /usr/local/libexec/rundump failed or no dump program available:
> > Exec format error
> >...
> >I wouldn't be too bothered by a failure to execute because of root-nfs
> >access restrictions but I'd thought that Exec format errors where do
> >to architecture issues.
>
> Both of those programs are setuid root. If you're delivering them to
> the client via NFS, you may need to change your mount options (or the
> export options, I always forget which side controls it) to allow setuid.
> Irix may translate that problem into "exec format error".
>
> If that doesn't help, try logging on to the client and run:
>
> df /usr/local/libexec/rundump
> file /usr/local/libexec/rundump
>
> (run them as the Amanda user). The first will confirm the file is coming
> from where you think it should. The second should tell you about the
> architecture it was built for.
>
> > Brian
>
> John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
