AW: coherency between amindexd and amrecover

This is my inetd.conf! #inetd.conf of saturn # amanda backup server with indexing capabilities amandaidx stream tcp nowait root/usr/lib/amanda/amindexd amindexd amidxtape stream tcp nowait root/usr/lib/amanda/amidxtaped amidxtaped # # amanda backup client amanda

Re: AW: coherency between amindexd and amrecover

Jörn Hildebrandt wrote: This is my inetd.conf! #inetd.conf of saturn # amanda backup server with indexing capabilities amandaidx stream tcp nowait root/usr/lib/amanda/amindexd amindexd amidxtape stream tcp nowait root/usr/lib/amanda/amidxtaped Why root

AW: coherency between amindexd and amrecover

NOTES: taper: tape DailySet101 kb 178464 fm 1 [OK] ok, i hope you can help me! thanks Jrn, a trainee at system elektronik AW: coherency between amindexd and amrecover The first time, i was able to login via telnet on port 10082, so that's why i think it must be now also possibl

Re: AW: coherency between amindexd and amrecover

i didn't type anything to telnet before i got this report for port 10082: saturn:~ # telnet saturn 10082 Trying 10.0.0.56... Connected to saturn. Escape character is '^]'. amindexd: could not open conf file "amanda.conf": No such file or directory Connection closed by foreign host. Please post