I also keep old versions, but automatically updating could be a problem. What happens when there's a bug in a newer version that caused crashing but the (sometimes sole) admin isn't around? I always schedule updates when I know I will be available to test in our environment first.
I'm all for sending out notices of minor and critical updates, maybe even annoying the admins with a popup every time there's a new version, but autoupdates are a bad idea for a system as critical as an antispam server. On Thu, Nov 26, 2009 at 2:25 AM, GrayHat <gray...@gmx.net> wrote: >> I'd second this functionality- because this is basically what I do >> manually now anyway. That way if things really screw up, I can go >> back and rename the old file and regain the previous version's >> functionality until the new one is fixed. > > Well... that's what I've been doing for a lot of time now; I've a > folder called "backups" sitting under the ASSP folder and > each time a new version comes out, I copy the current assp.pl > as backups/asspNNNN.pl (where NNNN is a number), then > I replace assp.pl with the latest version and restart ASSP; this > way if the latest version has some problem I can rollback to > the latest one... or even (rarely needed) roll back some more > versions to find out if an older one doesn't have the problem > by the way, having ASSP automagically backup itself would > be a BIG plus; in such a case, the auto-update mechanism > should imHo work this way > > * The version check should run before starting the "rebuildspamdb" > but using the same schedule > > * At the desired time ASSP will check for the presence of a new > version, and, if present fetch the "update-notice" from the home > site and then > > ** if autoupdate is disabled it will just send a notification email > containing the "update-notice" contents > > ** if autoupdate is enabled it will: > > *** fetch the updated assp.pl into a temp folder (or using a temp name) > and > if the fetch is successful (it may be useful to also fetch a > checksum file > and verify if the downloaded assp is ok) it will > > **** backup the current ASSP to the backup folder as > ASSP.version.release.pl > (proceed only if backup was successful) > > **** copy the new assp.pl in place and restart ASSP > > this way an admin may decide if either use the automatic update or if he > just want to receive update notifications and proceed to manual update, > the notification will ALSO contain some notices so that, in case of a > bugfix > release or (let's hope won't be needed) in case of a vulnerability he'll > get a notice about the issue and the need to update asap > > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Assp-test mailing list > Assp-test@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/assp-test > ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Assp-test mailing list Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test
