Hi all,

There is something very, but very, strange that is happening to me.
when i start amcheck from my server,  inetd on the client machine starts 
to eat more and more cpu ressources up to 98%, and event though the 
amcheck process stops by giving me a "selfcheck request failed on 
client", inetd keeps bursting on the client.

The only thing i did from the other times was a test with amrecover 
(both from server and from client, and both worked perfectly).

If i kill inetd on the client and restarts it it goes back to normal, 
but does nothing with a HUP signal.

The only entries in inetd.conf are the amanda ones, so its not any other 
program that is interfering.

If anyone has a clue of what is happening, help would be greatly 
appreciated.

Thanks

Reply via email to