robert wrote at 2003-9-23 12:57 +0200:
> it seams that the Product XRON does not work with python 2.2.
>
> I can create an instance, however when I try to enter into it from the zmi, I
> get an error:
> The object at http://localhost:8080/sprint/scheduler has an empty or missing
> docstrin
it seams that the Product XRON does not work with python 2.2.
Perhaps you should be thankful .. We tried to use xron a year
or so ago, and it bit us repeatedly. We dropped it and use
cron to tickle a Zope URL or to call an external method. For
those, see:
http://mail.zope.org/pipermail/zope/2003-Fe
Homan Els wrote:
> ZOPE 2.2.2 , Xron -0-0-9, Python 1.5.2
>
> Hi Steve,
>
> I am running Zope under linux (Suse 6.4). And I would like to use
> Xron. But, I can not get it running.
> I did read your email : Xron on linux. And therefore I would like to
> know, how you did manage to use Xron.
On Thu, 24 May 2001, Loren Stafford wrote:
> 5. You can truncate the bloated tail end of a Data.fs file using standard
> system tools. I don't remember how right at the moment, but a search in the
> mail archives on trucate and data.fs might be fruitful.
Use the unix command 'split'. I immagin
1. If you can use the management interface, you can disable a Xron Scheduled
Method by deleting it from the Schedule catalog or setting its reschedule
interval to null.
2. If you delete (or just rename __init__.py to something else in) the Xron
Product. And restart Zope, there will be no Dispatch
Hi,
Could you please send your external python method. + Product for using in
combination with a cron job.
Because, this can really help me a lot.
Thanks,
Els
Nicholas Lo wrote:
> Sorry man, I still have the same problem :( However, instead I use Xron, I
> write a simple product which is
This is a known problem. Search back thru the archives of [EMAIL PROTECTED] for
Xron and you will find some helpful information. I'll also try to find the
relevant email and forward it to you separately.
-- Loren (lstaffor)
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PR
>Yes, using Client.py was the easiest way to do that. The biggest problem
>with Client.py is its dependency on HTTP. If your server is set up to
>only accept HTTPS, then you can't use Xron -- not a desirable trade-off.
If security is the problem, you could configure the HTTP part to
listen only o
> > What if you want a small job to be done every 30 seconds?
>
> I generally don't... I'm satisfied with cron granularity, although
others
> might not be. Do you have this requirement?
I thought a little about the granularity issue and decided to go with
the most general solution. I have no req
From: "Chris McDonough" <[EMAIL PROTECTED]>
> > > As a side note, I do not like the fact that Xron requires you to
use
> special
> > > DTML methods. I suppose this is a requirement in this
architecture due
> to
> > > the fact they need to be autocataloged, but I don't really like
that
> featur
From: "Kapil Thangavelu" <[EMAIL PROTECTED]>
[snip]
> > > Xron has a single dispatcher thread. This thread knows how long to
sleep
> > > for until the next job needs to run.
>
> this model has problems when new jobs (for immeadiate execution) are
> entered after the system sleeps. i think it sh
From: "Chris McDonough" <[EMAIL PROTECTED]>
[snip]
> As a side note, I do not like the fact that Xron requires you to use
special
> DTML methods. I suppose this is a requirement in this architecture
due to
> the fact they need to be autocataloged, but I don't really like that
feature
> either
> > Do you think this is this any more effective than having a producer
thread
> > do a lookup every minute to see what jobs are current, after which it
should
> > put the current jobs in a queue? E.g., as the "run" method of a
separate
> > producer thread:
>
> the same problem applies, a solutio
A smoke break later, some possible more thoughts and snake oil,
there are two general purpose facilities embodied in xron that i would
like to see made available as zope services, async zope processing and
scheduling.
async-- i'd like to be able to designate TTW that a method execute
outside of
Chris McDonough wrote:
> >
> > > > Xron has a single dispatcher thread. This thread knows how long to
> sleep
> > > > for until the next job needs to run.
> > >
> > > Do you think this is this any more effective than having a producer
> thread
> > > do a lookup every minute to see what jobs are c
Chris McDonough wrote:
>
> > It is the Xron DTML Method's responsibility to reschedule itself.
> > It could be its first duty, however. Then again, as all the work happens
> > inside a ZODB transaction, it doesn't matter when the reschedule
> > happens.
>
> I understand.
>
> As a side note, I
> I'll need to try to call get_transaction().commit() from a
> manually-constructed Python thread fired off from Zope and see what
happens.
> I think it'll just work. I'll find out in a few minutes. :-)
Yes, it just works. :-)
___
Zope-Dev maillis
> > As a side note, I do not like the fact that Xron requires you to use
special
> > DTML methods. I suppose this is a requirement in this architecture due
to
> > the fact they need to be autocataloged, but I don't really like that
feature
> > either :-).
>
> I think Xron could work with anything
Chris McDonough wrote:
>
> As a side note, I do not like the fact that Xron requires you to use special
> DTML methods. I suppose this is a requirement in this architecture due to
> the fact they need to be autocataloged, but I don't really like that feature
> either :-).
I think Xron could wor
> It is the Xron DTML Method's responsibility to reschedule itself.
> It could be its first duty, however. Then again, as all the work happens
> inside a ZODB transaction, it doesn't matter when the reschedule
> happens.
I understand.
As a side note, I do not like the fact that Xron requires you
Chris McDonough wrote:
>
> Steve,
>
> I am also interested in scheduling... though I haven't looked closely at
> Xron.
>
> > The Xron product seems rather "fragile" in use.
> >
> > That is, if things go wrong when an Xron DTML Method is triggered, that
> > method doesn't get rescheduled.
>
> D
Steve,
I am also interested in scheduling... though I haven't looked closely at
Xron.
> The Xron product seems rather "fragile" in use.
>
> That is, if things go wrong when an Xron DTML Method is triggered, that
> method doesn't get rescheduled.
Does Xron take an optimistic approach to repeati
Loren Stafford wrote:
>
> Thanks, Steve.
>
> I have few questions below 8-) (I'm always better with questions than
> answers.)
>
> -- Loren
>
> From: "Steve Alexander" <[EMAIL PROTECTED]>
> > Hi Loren,
> >
> > > I'd be glad to listen to well considered proposals for how Xron should
> > >
Thanks, Steve.
I have few questions below 8-) (I'm always better with questions than
answers.)
-- Loren
From: "Steve Alexander" <[EMAIL PROTECTED]>
> Hi Loren,
>
> > I'd be glad to listen to well considered proposals for how Xron should
> > handle security.
>
> Consider this a "straw man".
24 matches
Mail list logo
