>... I have gone through the archives and
>tried all of the steps suggested in all of the archived articles on this
>subject without success. ...
The outputs you posted look reasonable.
>... other than that the amandad
>service was looping and xinetd was killing it. ...
OK, then it's something about the way xinetd is starting amandad
that's bad. And it's happening right away before amandad can get even
barely started.
One possibility is that you should probably add "groups = yes" to the
xinetd amandad config file so it gets started with the alternate groups.
The default is to only let it have its primary group.
I'd suggest going back to the script and truss tests. One possiblity for
why they didn't work before is that after xinetd terminates a service, it
leaves it dead for several minutes and isn't even listening. That would
look the same from the amcheck side -- host down -- but for a totally
different reason. Before each and every test, do a refresh of xinetd
and "netstat -a | grep amanda" to be sure someone is listening.
>Mark A. Holm
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
