location of error log for a specific siteaccess

«

Previous topic

|

Install & configuration

|

Next topic

»

Author	Message
Claudia Kosny	Friday 09 February 2007 4:45:19 am Hi there Is there a way to specify the location of the error log for each siteaccess? I have quite a few siteaccesses which use the same database but different templates and settings and it would be nice to have the errors separate for each siteaccess. The setting LogDir in [FileSettings] in site.ini just determines the location of the storage.log and I could not find any other suitable setting or ini file. Thanks Claudia
Yves B	Monday 26 March 2007 8:30:45 am Hi, I'd also like to monitor separately the public site from administrative site. LogFiles are hard coded in EzDebug, may be because some errors may be traced before knowing the siteaccess ? The shortest way I found was to change ezDebug "writeFile" to include from : $logDir = $logFileData[0]; $logName = $logFileData[1]; to : $ini =& eZINI::instance(); $logSite = $ini->variable( 'SiteSettings', 'SiteURL' ); $logDir = $logFileData[0]; $logName = $logSite.'_'.$logFileData[1]; It suits my needs, and, I think, maintains log rotation.
Felix Woldt	Monday 26 March 2007 11:10:16 am This is a bug. Have a look to this bugreports: http://issues.ez.no/IssueView.php?Id=8397&activeItem=6 http://issues.ez.no/IssueView.php?Id=10366 http://www.jac-systeme.de - Developers united in eZ Publish: http://www.cjw-network.com CJW Newsletter 1.0.0 released: http://projects.ez.no/cjw_newsletter
Łukasz Serwatka	Tuesday 27 March 2007 12:18:48 am Hi, Fix for this issue is addressed for next eZ Publish 3.9.2 sub-release. Personal website -> http://serwatka.net Blog (about eZ Publish) -> http://serwatka.net/blog
meinhard benn	Monday 30 March 2009 2:12:12 pm This bug is back, because the fix had been reverted. See my comment: http://issues.ez.no/IssueView.php?Id=10366&ProjectId=3#Comment261080 http://goozee.benn.org/ - Google Co-op for eZ sites

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.

eZ debug

Timing:	Jan 18 2025 16:00:40
Script start
Timing:	Jan 18 2025 16:00:40
Module start 'layout'
Timing:	Jan 18 2025 16:00:40
Module start 'content'
Timing:	Jan 18 2025 16:00:40
Module end 'content'
Timing:	Jan 18 2025 16:00:40
Script end

Main resources:

Total runtime	0.0179 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.0051	588.1641	152.6563
Module start 'layout'	0.0051	0.0034	740.8203	39.5078
Module start 'content'	0.0084	0.0063	780.3281	93.3984
Module end 'content'	0.0147	0.0031	873.7266	34.3047
Script end	0.0178		908.0313

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0036	20.2628	14	0.0003
Check MTime	0.0011	6.2727	14	0.0001
Mysql Total
Database connection	0.0007	4.1640	1	0.0007
Mysqli_queries	0.0032	18.0582	3	0.0011
Looping result	0.0000	0.0840	1	0.0000
Template Total	0.0017	9.7	1	0.0017
Template load	0.0009	5.2783	1	0.0009
Template processing	0.0008	4.4332	1	0.0008
Override
Cache load	0.0006	3.5495	1	0.0006
General
dbfile	0.0002	1.2529	8	0.0000
String conversion	0.0000	0.0493	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