> Off the top of anyone's head, one of two servers I have to do is > rather busy, might there be anything from experience out of the > ordinary I might need to consider?
I'd start by making a full backup (tgz or the like) of the current "assp" folder (you won't need to backup the spam/notspam folders) and subfolders contents; that shouldn't be needed but... better staying on the safe side, and such a backup will allow you to rollback your setup if needed next proceed using the module installation script to ensure you'll install all the needed modules, then, replace assp.pl and rebuildspamdb.pl into the assp folder, stop assp and run the rebuildspamdb from cmdline, then restart the assp from cmdline again (no daemon mode) to be able to see any startup errors (also check the log) if all ok, stop assp and start it as a daemon that way your config and your custom files will remain the same, now open the ASSP gui and proceed revising the settings and changing any additional setting, then even if you didn't change anything, click the "apply changes" button to force assp to write any missing value to the config file (using default values) ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
