> What's your inetd.conf line look like? If you forget the trailing
> command name argument, I've seen amandad fail like this on some systems.
No changes...
amanda dgram udp wait amanda /usr/local/libexec/amandad amandad
> What happens if you run amandad by hand **as the Amanda user**?
(*insecure*)amanda@atsun01:/usr/local/libexec$ ./amandad
Segmentation Fault
> Is /tmp/amanda/amandad*debug being updated? If Amanda gets that far,
> you should have a core file (or several :-) in /tmp/amanda.
Yes, /tmp/amanda/amandad*.debug is being updated when amandad is run by hand
(as user amanda)
I get no core dumps though :(
> Run a debugger against amandad and one of them to get a stack traceback.
(gdb) run
Starting program: /usr/local/libexec/amandad
warning: Lowest section in /usr/lib/libintl.so.1 is .hash at 00000074
Program received signal SIGSEGV, Segmentation fault.
0xff0b6e94 in strlen () from /usr/lib/libc.so.1
(gdb) quit
> John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Thanks,
-Ben
