> The signals are only within the same process, though. They don't wake up > other processes (they are not UNIX signals). Fortunately, the process > started by your cronjob can just import any bits of Django it might need > (e.g. for accessing models) and do the work directly.
I currently have the cronjob do an HTTP GET on a certain view. Although that does work, it has the disadvantage that the cronjob should identify itself (else anybody could invoke the view). It would be nice if the cronjob could directly invoke some python code that has access to the django modules, as you say. I'll try that next. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
