Cut and paste ...............
it only croaks on the amcheck.......
no security packs. at all:
the amandad will Hangup before providing any output..........
John R. Jackson wrote:
>>amanda dgram udp wait amanda /var/adm/amanda/libexec/amandad
>>amandad
>>amandaidx stream tcp nowait amanda /var/adm/amanda/libexec/amindexd
>>amindexd
>>amidxtape stream tcp nowait amanda /var/adm/amanda/libexec/amidxtaped
>>amidxtaped
>>
>
>The lines came across in the E-mail broken as shown above. Is that
>real or is it just a cut/paste artifact?
>
>The important part is that there be one, and only one, arg to each of
>the lines (after the path to the executable). If the arg (e.g. "amanda")
>is missing, the server will try to reference argv[0] and die.
>
>What you have above is OK if there are actually three lines and not six.
>
>Did inetd whine into /var/adm/messages when you HUP'd it?
>
>Do you have (I think it's called) BSM installed (some kind of enhanced
>security package)? I recall problems with it, but don't remember the
>details.
>
>If none of that helps, here are the next things I do (from my inetd.conf):
>
>#JJ First debug trick -- create this shell script (chmod +x /tmp/amandad.test):
>#JJ #!/bin/ksh
>#JJ exec > /tmp/amandad.out.$$ 2>&1
>#JJ echo "$(/bin/date): starting amandad ($#): " "$@"
>#JJ /opt/amanda/libexec/amandad "$@"
>#JJ status=$?
>#JJ echo "$(/bin/date): amandad done: status is $status"
>#JJ exit $status
>#JJ
>#JJ amanda dgram udp wait backup /tmp/amandad.test amandad
>#JJ
>#JJ Next debug trick -- run amandad under truss:
>#JJ
>#JJ amanda dgram udp wait backup /bin/truss amandad -fo
>/tmp/amandad.truss /opt/amanda/libexec/amandad
>
>Note that the user name ("backup" vs. "amanda") and paths to the binaries
>on your system will be different.
>
>John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
>
