Another way to pass the parameters to runcronjobs.php

Next topic

Author	Message
Javier Magán	Wednesday 28 July 2010 12:33:46 pm Hello. Is it possible to pass the prarameters to the runcronjobs.php script as ...mysite.com/runcronjobs.php?parameter1=xx&parameter2=yy Aparently, my ISP only suports this format for configuring cronjobs (no ssh access). If posible, how should this one be?: php runcronjobs.php -s site_admin sendmail Thanks
Gaetano Giunta	Wednesday 28 July 2010 12:45:12 pm Afaik, it is not possible - it would also be considered a big securoty breach if it was - any user could trigger execution of existing cronjobs with teh desired parameters... Otoh it might be interesting to wrap the runcronjobs script in a properly secured module+view. The problem is timeouts and excessive memory usage... The ezscriptmonitor extension should be the solution for these kind of needs Principal Consultant International Business Member of the Community Project Board

Author

Message

Wednesday 28 July 2010 12:33:46 pm

Hello.

Is it possible to pass the prarameters to the runcronjobs.php script as ...mysite.com/runcronjobs.php?parameter1=xx&parameter2=yy

Aparently, my ISP only suports this format for configuring cronjobs (no ssh access).
If posible, how should this one be?:

php runcronjobs.php -s site_admin sendmail

Thanks

Gaetano Giunta

Wednesday 28 July 2010 12:45:12 pm

Afaik, it is not possible - it would also be considered a big securoty breach if it was - any user could trigger execution of existing cronjobs with teh desired parameters...

Otoh it might be interesting to wrap the runcronjobs script in a properly secured module+view. The problem is timeouts and excessive memory usage...

The ezscriptmonitor extension should be the solution for these kind of needs

Principal Consultant International Business
Member of the Community Project Board

eZ debug

Timing:	Jan 29 2025 23:52:12
Script start
Timing:	Jan 29 2025 23:52:12
Module start 'layout'
Timing:	Jan 29 2025 23:52:12
Module start 'content'
Timing:	Jan 29 2025 23:52:12
Module end 'content'
Timing:	Jan 29 2025 23:52:12
Script end

Main resources:

Total runtime	0.0119 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.0039	588.3828	151.2422
Module start 'layout'	0.0039	0.0022	739.6250	36.7266
Module start 'content'	0.0061	0.0045	776.3516	90.2188
Module end 'content'	0.0106	0.0012	866.5703	29.9922
Script end	0.0118		896.5625

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0020	16.9029	14	0.0001
Check MTime	0.0010	8.2677	14	0.0001
Mysql Total
Database connection	0.0007	5.6176	1	0.0007
Mysqli_queries	0.0019	16.2042	3	0.0006
Looping result	0.0000	0.1586	1	0.0000
Template Total	0.0010	8.1	1	0.0010
Template load	0.0008	6.7037	1	0.0008
Template processing	0.0002	1.3652	1	0.0002
Override
Cache load	0.0006	4.8928	1	0.0006
General
dbfile	0.0012	10.0707	8	0.0001
String conversion	0.0000	0.0522	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.0002 secs