>This is what the amrecover sends to stdout:
>
> AMRECOVER Version 2.4.1p1. Contacting server on localhost ...
> amrecover: Unexpected server end of file
>
>And this is what I found in /var/log/messages:
>...
> Jan 29 07:52:07 myhost xinetd[1318]: warning: can't get client
>address: Invalid argument
Stan Brown worked on this almost a year ago and came up with the following
patch, which I lost in my inbox (sigh). Please give it a try and let
me know if it works so I can (finally) get it into a release.
> Jan 29 07:52:07 myhost xinetd[1318]: file descriptor of service
>amandaidx has been closed
>...
>This happens only the very first time, if I try to connect
>via amrecover the next time, nothing happens in the syslog,
>but the amrecover client barfs:
>
> AMRECOVER Version 2.4.1p1. Contacting server on localhost ...
> amrecover: Error connecting to server: Connection refused
That's because xinetd was **very** unhappy :-) and shut down the amandaidx
service (see the message it logged). So there isn't anyone listening
any more.
I don't know how xinetd does it, but other versions of inetd will reenable
a service after (e.g.) 10 minutes, or if you HUP them.
>Sebastian
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
amrecover.diff
