On Wed, Jul 19, 2006 at 10:46:18AM -0600, Chris Cameron wrote:
> On Tue, 2006-07-18 at 17:36 -0700, Kevin Till wrote:
> > 
> > what is the amanda entry in /etc/inet/inetd.conf?
> 
> amanda  dgram   udp     wait    root    /opt/amanda/libexec/amandad
> amandad
> 
> 
> > Try "truss /opt/amanda/libexec/amandad" and see if there is anything 
> > obviously wrong.
> 
> Only thing that doesn't look normal to me:
> 
> open("/usr/platform/SUNW,Sun-Fire-V240/lib/libc_psr.so.1", O_RDONLY) = 3
> mmap(0xFF230000, 8192, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED, 3, 0)
> = 0xFF230000
> close(3)                                        = 0
> brk(0x00024098)                                 = 0
> brk(0x00026098)                                 = 0
> sysconfig(_CONFIG_STACK_PROT)                   = 7
> fcntl(0, F_GETFD, 0x00000000)                   = 0
> fcntl(1, F_GETFD, 0x00000001)                   = 0
> fcntl(2, F_GETFD, 0x00000001)                   = 0
> close(3)                                        Err#9 EBADF
> close(4)                                        Err#9 EBADF
> close(5)                                        Err#9 EBADF
> close(6)                                        Err#9 EBADF
> close(7)                                        Err#9 EBADF
> 
> 
> The close()'s go all the way to 1023. After that it goes on to writing
> its debug output to /tmp/amanda.
> 
> 
> I don't know what they mean, but could all those close()'s be the cause?

Shouldn't.  Amanda knows what file descriptors it will need.
As a security measure, most amanda commands, at start-up,
close all file descriptors that will not be needed.

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