For a variety of reasons I really would like to see rebuildspamdb.pl be available outside of ASSP again. Here are a list of 6 reasons why.
1.) By having rebuild spam invoked and running under the ASSP process, you put a load on that process for no reason. When I ran rebuildspamdb last night, which is a single threaded process. I saw 2 processes for ASSP running at 100%. If rebuildspamdb was its own process, it would run at 100%, and allow ASSP to run at its normal CPU usage, which is VERY low. It would not create additional load for ASSP. Also any problems rebuidspamdb has will directly effect the ASSP process. It could crash or hang ASSP for no reason. If it was separate, that could NEVER happen. 2.) When you can run rebuildspamdb on its own, you can renice the process and control how much resources its consuming. To keep it from interfering with ASSP and/or taking resources away from processing mail. 3.) You can use cron to schedule rebuilding the spam db. You do not need another per module. Which consumes more resources, that would not be consumed or used otherwise. Schedule cron if nothing else does add a bit more overhead. All Unix based systems will have a cron daemon, so why add another piece of software when the system already has such. Even Windows has task scheduler. Programs should not need to replicate functionality the OS already provides. 4.) You cannot use another machine to rebuild the spam db, as it has to be run from within ASSP. Unless you install ASSP on another machine just to be able to rebuildspamdb on another. Think if assp files are on a NFS share mounted by more than on server. You could put the load of rebuilding spam database on a completely different machine. One could even fire up a VM just to rebuild the spamdb with lots of resources and have that done very quickly. 5.) Combining rebuildspamdb into assp goes against the Unix philosophy. Qmail is a great example, it has TONS of binaries, that usually chain together to make qmails functionality. Qmail does NOT combine multiple things into a single binary. Nor is one required to invoke the other. Most any binary installed by qmail can be invoked by another qmail binary, third party binary or script. http://en.wikipedia.org/wiki/Unix_philosophy 6.) Your changing an over decade old way of doing things with ASSP v1, and there is little to no benefit. Its fine if rebuildspamdb is modified and can by run from within ASSP itself. By why not leave it so rebuildspamdb can be run on its own as it was with ASSP v1. Removing choice and the old way of doing things, forcing all to go a direction that is not superior and comes with more overhead makes little to no sense. There are likely more, but I think 6 solid reasons are good enough. I doubt 6 solid reasons can be provided to justify rebuildspamdb being run by ASSP and no ability to run directly as it you could with ASSP v1. -- William L. Thomson Jr. Obsidian-Studios, Inc. http://www.obsidian-studios.com This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. ------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Assp-user mailing list Assp-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-user
