>... Now, amandad will not run from
>inetd, although I can launch it from the command line without a problem.
First, make sure the inetd.conf line is correct. In particular, that
argv[0] is specified.
If that doesn't help, here are my two standard tricks for debugging
this problem:
* Create a shell script like this someplace (e.g. /tmp/amandad.test:
#!/bin/ksh
exec > /tmp/amandad.out.$$ 2>&1
print "$(date): starting amandad"
/usr/local/libexec/amandad
print "$(date): amandad done: status is $?"
exit 0
Make the script executable (chmod +x), then change your inetd.conf
line to call it instead of amandad directly (change the user name
to match your setup):
amanda dgram udp wait <AMANDA> /tmp/amandad.test amandad
See what shows up in /tmp/amandad.out.
* Run amandad under truss:
amanda dgram udp wait backup /bin/truss amandad -fo /tmp/amandad.truss
/usr/local/libexec/amandad
Look through /tmp/amandad.truss for errors, in particular the last
several system calls.
>Kevin
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
