The obvious solution seems to be use a cron job, instead of trying to strongarm django/apache into doing something that they aren't for.
There is no reason your cron job couldnt be a python script that uses django classes/your model etc. if you want. Tom On Sun, Sep 28, 2008 at 8:11 PM, Julian <[EMAIL PROTECTED]> wrote: > > hi there, > > i have written a middleware-class wich is doing what a cronjob should > do. it is doing some backup-stuff, and repeats that every 12 hours. it > is a thread and is placed in the list of middleware-classes, but not > processing any request or overwriting any typical method for a > middleware class. > > my problem is: with the devlopment-server it's created once. with > mod_python and _three_ apache instances, there are three instances of > my backup-thread, but i want to have only one. > > how can i start a thread (without having an extra cronjob) in my > django-app only once on the whole server??? the hackish solution would > be to store the actual PID on a special place. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---