Use of alternate VAR directory

Next topic

Author	Message
Vivienne van Velzen	Wednesday 07 July 2004 5:10:19 am Hi all, I'm using one EzPublish installation for multiple sites. To keep the sites somewhat apart, I created different VAR directories for each site (defined in the site's site.ini.append.php). Just now I came across the fact that EZ still uses the default VAR directory for some caching (/var/cache/ini/ and /var/cache/codepages/) and logging (/var/log/). Is there any setting that points EZ towards my custom VAR directory for these as well? TIA, Vivienne
Bård Farstad	Wednesday 07 July 2004 5:13:42 am These use the common var directory because they're not different for the different sites. E.g. the codepage cache files will be the same for all sites, same goes for the .ini cache. -bård Documentation: http://ez.no/doc
Vivienne van Velzen	Wednesday 07 July 2004 5:56:18 am Thanks for the speedy reply. And what about the log-directory? I assume warnings etc. are specific for each site? Greetings, Vivienne

Author

Message

Wednesday 07 July 2004 5:10:19 am

Hi all,

I'm using one EzPublish installation for multiple sites. To keep the sites somewhat apart, I created different VAR directories for each site (defined in the site's site.ini.append.php).
Just now I came across the fact that EZ still uses the default VAR directory for some caching (/var/cache/ini/ and /var/cache/codepages/) and logging (/var/log/).
Is there any setting that points EZ towards my custom VAR directory for these as well?

TIA,

Vivienne

Bård Farstad

Wednesday 07 July 2004 5:13:42 am

These use the common var directory because they're not different for the different sites. E.g. the codepage cache files will be the same for all sites, same goes for the .ini cache.

-bård

Documentation: http://ez.no/doc

Vivienne van Velzen

Wednesday 07 July 2004 5:56:18 am

Thanks for the speedy reply. And what about the log-directory? I assume warnings etc. are specific for each site?
Greetings,

Vivienne

eZ debug

Timing:	Jan 20 2025 00:26:09
Script start
Timing:	Jan 20 2025 00:26:09
Module start 'layout'
Timing:	Jan 20 2025 00:26:09
Module start 'content'
Timing:	Jan 20 2025 00:26:09
Module end 'content'
Timing:	Jan 20 2025 00:26:09
Script end

Main resources:

Total runtime	0.0141 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.0043	589.1563	152.6250
Module start 'layout'	0.0043	0.0036	741.7813	39.4609
Module start 'content'	0.0080	0.0042	781.2422	89.3203
Module end 'content'	0.0121	0.0020	870.5625	30.3047
Script end	0.0141		900.8672

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0022	15.8013	14	0.0002
Check MTime	0.0010	7.1519	14	0.0001
Mysql Total
Database connection	0.0006	4.1957	1	0.0006
Mysqli_queries	0.0030	21.2617	3	0.0010
Looping result	0.0000	0.1686	1	0.0000
Template Total	0.0016	11.4	1	0.0016
Template load	0.0009	6.0541	1	0.0009
Template processing	0.0008	5.3340	1	0.0008
Override
Cache load	0.0006	4.2294	1	0.0006
General
dbfile	0.0002	1.3744	8	0.0000
String conversion	0.0000	0.0573	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