On Saturday, January 24, 2015 06:57:18 PM Thomas Eckardt wrote: > >But again without schedule cron module, there is no > >automation of spam db rebuild as it seems. > > Yes , you are right. The option to define only the runtime hour was > removed some times ago from this configuration parameter - I'm sorry, I > simply forgot this. > The same applies to the Restart Scheduler ! > As I wrote in any of my last posts, both option are using the > Schedule::Cron modules really.
So without that module, the spamdb is never rebuild unless done manually. Even if rebuild spamdb will be run/invoked from ASSP. I fail to see why it cannot still be invoked on its own outside of ASSP. I think that functionality should be added back as that is how it has been for a long time. Then for anyone who wants they can install the schedule cron module and have ASSP deal with that internally if they so choose. Either way the option should be there. Options are good, lack there of is NOT. Not to mention Unix rubber band ball philosophy, you make small programs that do single jobs well. Then you couple those with other programs. Thus combining functionality into a single program goes against that approach. It also makes finding bugs more difficult. Am I experiencing an issue with ASSP or rebuilding spam db? Hard to say given they are both one. If I could rebuild the spam db outside of ASSP, then I could begin to start tracking down the issue. Or at least say its this or that, ASSP itself and/or the rebuild spam db process. > Currently I'm the only one on this planet who knows simply everthing about > assp, except the things, which nobody knows or the things I forgot :):) Not sure how encouraging that is, given you said the schedule cron module was not required and it is. I would assume the developer to be aware of such trivial things. Then again I understand forgetting things just the same. I cannot recall every line of code I have written, why I wrote that, what it does, etc. > from the lines 18 and 19 of assp.pl V2 > > # ASSP V2 pro development since 2.0.0 by > # Thomas Eckardt > > from the assp.pl V1 > > # ASSP V1 development since 1.9.9 14155 by Thomas Eckardt & John Calvi > # ASSP V2 pro development since 2.0.0 by Thomas Eckardt > > You don't believe me ? Than don't use assp. I don't believe the system requirements you stated. I took you at your word about schedule cron not being required till it seemed otherwise. I am simply stating there are others who are familiar with ASSP as well. Developers are familiar with what they right, users are familiar with what they use. My clients routinely use software in ways I never intended, which can cause issues etc. I am some what glad Fritz is no longer doing development, his QA was interesting to say the least. That said I have been around long enough to see the change of guard/developers for ASSP a few times. I have thought of getting involved, but I would port it to Java or C. I might look into re-writing the rebuild spamdb in C. I would not do that in Java even if I re-wrote ASSP in Java. Given that it runs often, is resource consuming, etc. Its a prime candidate for a C application. Like the asspr application I wrote some time ago. Which I recently discovered has a pretty major bug causing seg faults if you run it on less than 3 folders, discarded spam, and viruses. If 1 or 2 folders it seg faults, I need to fix that and issue a new release. Perl might have made sense over a decade ago when ASSP was first written. Also likely used for rapid application development not long term performance, etc. It likely would have been best to be ported long ago. ASSP is one of if not the only server application I run that is not C or Java. -- 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. ------------------------------------------------------------------------------ New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet _______________________________________________ Assp-user mailing list Assp-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-user
