In no case should there be a reason to write the file "/etc/amandates" if it already exists. Here's why: a) If file exists and AMANDA package was never used by the User, then the file is empty and therefore no need to replace the empty file with another empty file. b) If file exists and AMANDA package is in use by the User, then the file contains important mutable data written by the AMANDA system. Therefore the file should not be disturbed. Conclusion: If "/etc/amandates" file exists, then do not include the file in the list to be updated via dispatch-conf or the former tool that performed same. Reproducible: Didn't try Steps to Reproduce: Occured when I emerge'd amanda. Emerge system upgraded from version 2.4.4_p2-r1 to version 2.4.4-r3 Actual Results: dispath-conf asks to replace the config file... But, that is just it... It is not a config file... It is mutable data which is written to disk by AMANDA system. Writing over this file adversely affects AMANDA state information. Expected Results: Conclusion: If "/etc/amandates" file exists, then do not include the file in the list to be updated via dispatch-conf or the former tool that performed same. The idiosyncrasy here that should not be forgotten is this: Unless AMANDA has changed since I last configured it manually, AMANDA required the system administrator to "touch" the file "/etc/amandates" into existence (and set the appropriate file ownership attributes). IIRC, the AMANDA program would not create this file on its own.
fixed in cvs.
