One instance of a cronjob at given time ? why ?

Next topic

Author	Message
Slawek Machul	Monday 14 April 2008 7:37:29 am I'm wondering why there is not allowed more than one instance of the same cronjob script to be run at given time. If anyone may answer ? -- thank you
Piotrek Karaś	Monday 14 April 2008 9:06:30 am That's not true - this is why there are cronjobs parts - they group tasks that can be scheduled to run together: http://ez.no/doc/ez_publish/technical_manual/4_0/features/cronjobs/configuring_cronjobs http://ez.no/doc/ez_publish/technical_manual/4_0/reference/configuration_files/cronjob_ini Hope this helps. PS. My apologies! I might have misunderstood you... do you mean the exactly same job? twice in one setting for example? What would be the reason for that? -- Company: mediaSELF Sp. z o.o., http://www.mediaself.pl eZ references: http://ez.no/partners/worldwide_partners/mediaself eZ certified developer: http://ez.no/certification/verify/272585 eZ blog: http://ez.ryba.eu

Author

Message

Monday 14 April 2008 7:37:29 am

I'm wondering why there is not allowed more than one instance of the same cronjob script to be run at given time.
If anyone may answer ?

--
thank you

Piotrek Karaś

Monday 14 April 2008 9:06:30 am

That's not true - this is why there are cronjobs parts - they group tasks that can be scheduled to run together:
http://ez.no/doc/ez_publish/technical_manual/4_0/features/cronjobs/configuring_cronjobs
http://ez.no/doc/ez_publish/technical_manual/4_0/reference/configuration_files/cronjob_ini
Hope this helps.

PS. My apologies! I might have misunderstood you... do you mean the exactly same job? twice in one setting for example? What would be the reason for that?

--
Company: mediaSELF Sp. z o.o., http://www.mediaself.pl
eZ references: http://ez.no/partners/worldwide_partners/mediaself
eZ certified developer: http://ez.no/certification/verify/272585
eZ blog: http://ez.ryba.eu

eZ debug

Timing:	Jan 18 2025 20:53:24
Script start
Timing:	Jan 18 2025 20:53:24
Module start 'layout'
Timing:	Jan 18 2025 20:53:24
Module start 'content'
Timing:	Jan 18 2025 20:53:24
Module end 'content'
Timing:	Jan 18 2025 20:53:24
Script end

Main resources:

Total runtime	0.0249 sec
Peak memory usage	2,048.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0048	588.0469	152.6406
Module start 'layout'	0.0048	0.0032	740.6875	39.4766
Module start 'content'	0.0081	0.0146	780.1641	89.3672
Module end 'content'	0.0227	0.0022	869.5313	30.3047
Script end	0.0249		899.8359

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0027	10.9748	14	0.0002
Check MTime	0.0012	5.0045	14	0.0001
Mysql Total
Database connection	0.0006	2.5257	1	0.0006
Mysqli_queries	0.0029	11.6964	3	0.0010
Looping result	0.0000	0.0641	1	0.0000
Template Total	0.0015	6.0	1	0.0015
Template load	0.0008	3.2512	1	0.0008
Template processing	0.0007	2.7420	1	0.0007
Override
Cache load	0.0006	2.3525	1	0.0006
General
dbfile	0.0075	30.1058	8	0.0009
String conversion	0.0000	0.0239	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs