On Wed, 26 Sep 2001 at 6:46pm, Dave Brooks wrote > >So you started amandad, which started listening for requests, didn't hear > >any within 30 seconds, and so quit. That's normal. > > The daemon terminates itself if it doesnt receive any requests within 30 > seconds? So you have to restart it? Surely that can't be.
The daemon only starts up when a request comes in for it -- it's not running all the time. > 'amcheck std' produces no errors other than a timeout when trying to connect > to the client daemon. Well, that's a pretty important error... ;) What *exactly* does amcheck tell you? Is /tmp/amanda/amandad*debug or /tmp/amanda/selfcheck*debug getting updated when you amcheck? Is there any sort of a firewall/packet filter in place? You never told us OS... > The pertinent lines on the client's /etc/inetd.conf (which, for the time being, > happens to be the server as well) are as follows: > > amanda dgram udp wait amanda /usr/lib/amanda/amandad > amandad You mentioned xinetd, but now you're talking inetd... -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
