On Fri, 09 Jun 2006, Magnus Ihse Bursie wrote: > Sure, a check is better than nothing, but why not ask the user "Do you > want to keep your old settings, or remove them and replace with the new > amavis user?" or something like that? If you stumble upon this as part
I cannot replace an user, ever. It is too dangerous. Once, another amavis package (not amavisd-new) did a royal f***up: it created the amavis user with home set to /, which caused an userdel -r to rm -rf / and destroyed 30GB of data from an user. This is not a risk I am willing to take, ever. To this date amavisd-new has code to fix that bug (which was not ours, but an user trying to install amavisd-new and deciding to purge the old amavis user might be bitten by it...). I can force-change a lot of the information of an existing amavis user, like its name, groups, homedir. This will leave cruft behind, though, as we will never touch whatever else that user owned scattered on its old homedir, etc. The bottom line is that the local admin will have to clean up the mess, and the easiest way for him to do it is to **purge** all amavis packages, remove the user (if the other amavis* packages are leaving cruft behind: amavisd-new doesn't leave any), and install amavisd-new in a clean environment. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
