>Is there a way to determine what configuration options were compiled >into a particular amanda build? Is this the header information in the >top of an amandad.debug file? ...
Some of it is there. >If so, then where is there indication about '.amandahosts'? Look for "USE_AMANDAHOSTS". If it's there, you're using .amandahosts. >I have re-configured with the WITHOUT-amanda-hosts <sic> option ... I assume what you mean is you added --without-amandahosts to your ./configure line. Note there is **no** dash in "amandahosts". Did you remember to "make distclean" or "rm config.cache" before changing the ./configure argument list? If you want to see whether it made any difference after running ./configure but before actually building Amanda, look for USE_AMANDAHOSTS in config/config.h. >... I am still getting amandad debug files indicating an ERROR due to: > > "open of //.amandahosts failed" > > >which shows that, I do not have a home directory for amanda on this >client... Ummm, you *do* have a home directory, it's just that it's "/". There's nothing wrong with that. > My environment is on where rsh and hosts.equiv are routinely used. ln -s .rhosts .amandahosts >I did not think a home directory for the amanda user was necessary on >the amanda clients... especially if one was building for use without >the amandahosts file... You can't have a user without a home directory. The home may be shared with other users, but it can't not exist (well, I guess it can, but it is still defined in /etc/passwd even if the directory does not exist). The home directory will be required whether you use .amandahosts or .rhosts. The only thing different is which file is referenced. >jfk John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
