Kevin Chen wrote:

That's exactly what I have in inetd.conf, if I typed it from command
line, it would sit there for 30 seconds and stop and create a log file
at /tmp/amanda - amandad.20050316134621.debug.

Just as espected.  So that rules out library issues and
wrong wrong binaries.

Is there any amandad.*.debug file created when invoked through
inetd?

I would have a look again at the inetd.conf line too.
Maybe you have two lines and are looking at the wrong one.

I once had a problem (with samba instead of amanda) and even
when looking with three people on the inetd.conf line, we could
not find a mistake.  I just typed the line from scratch again,
no copy-paste or anything, and then it worked.  That gives the
conclusion that there must have been something wrong in the
other line (which we had already deleted), but I have two witnesses
that swear they did not see anything.
That was before I was abducted by The Aliens!!!  :-)


--
Paul Bijnens, Xplanation                            Tel  +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUM    Fax  +32 16 397.512
http://www.xplanation.com/          email:  Paul.Bijnens AT xplanation DOT com
***********************************************************************
* I think I've got the hang of it now:  exit, ^D, ^C, ^\, ^Z, ^Q, F6, *
* quit,  ZZ, :q, :q!,  M-Z, ^X^C,  logoff, logout, close, bye,  /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt,  abort,  hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e,  kill -1 $$,  shutdown, *
* kill -9 1,  Alt-F4,  Ctrl-Alt-Del,  AltGr-NumLock,  Stop-A,  ...    *
* ...  "Are you sure?"  ...   YES   ...   Phew ...   I'm out          *
***********************************************************************