You are not logged in.

#1 2008-04-03 09:31:57

Mikko777
Member
From: Suomi, Finland
Registered: 2006-10-30
Posts: 837

Phoronix Test Suite released and Result collection

So this might be "similar" to 3Dmark but for linux:
http://www.phoronix.com/scan.php?page=a … _pts&num=1

Also we could post some test results for referance,
Include Computer specs, and Distro you tested in.

We should run ./phoronix-test-suite benchmark universe but since it takes some time, ill post mine later.

Ugh and ofcourse it wont find time command roll

Edit:If someone gets this to work, please do give a shout.

Last edited by Mikko777 (2008-04-03 18:16:14)

Offline

#2 2008-04-04 04:59:07

coarseSand
Member
From: Ottawa, Canada
Registered: 2008-02-11
Posts: 203

Re: Phoronix Test Suite released and Result collection

Yeah, the PTS is pretty busted for me at the moment too. It's really more like the POS, if you catch my meaning. wink

It'll be fun to compare results once it works though. Good on the Phoronix guys for doing this.


vim? EMACS? Pssh, I code in Scribus.

Offline

#3 2008-04-04 07:22:11

iphitus
Forum Fellow
From: Melbourne, Australia
Registered: 2004-10-09
Posts: 4,927

Re: Phoronix Test Suite released and Result collection

Oh dear, gonna have kiddies left right and center posting their results. And 95% of them will be discountable because they were running compiz, firefox or some other application in background.

Offline

#4 2008-04-04 09:54:10

ibendiben
Member
Registered: 2007-10-10
Posts: 519
Website

Re: Phoronix Test Suite released and Result collection

iphitus wrote:

Oh dear, gonna have kiddies left right and center posting their results. And 95% of them will be discountable because they were running compiz, firefox or some other application in background.

A most tactful way of bringing the message:
     **************************************************************************
     * Be sure you're not running any applications in background, as it influences your stats. *
     **************************************************************************
roll

/mumbles: orareyoujustsayingit'ssolelykiddiesthatareusingArch?

Offline

#5 2008-04-04 17:08:22

coarseSand
Member
From: Ottawa, Canada
Registered: 2008-02-11
Posts: 203

Re: Phoronix Test Suite released and Result collection

Yeah, I'm going to shut down everything except for the command line when I run my benchmark. Not that any of this matters given the suite's current, non-functional state.


vim? EMACS? Pssh, I code in Scribus.

Offline

#6 2008-04-16 04:35:49

suolx
Member
From: Finland, Oulu
Registered: 2007-08-06
Posts: 29

Re: Phoronix Test Suite released and Result collection

I just tried to run the benchmark, but php gives no output? eg "php pts-core/pts-run-cmd.php LIST_SUITES"
nothing... any other dependencies than php?

Offline

#7 2008-04-16 08:12:33

Mikko777
Member
From: Suomi, Finland
Registered: 2006-10-30
Posts: 837

Re: Phoronix Test Suite released and Result collection

Guess most of the benchmarks are still broken in arch.
If and when this works it would be nice to compare 32 bit arch to 64 bit arch and against some other distro too (ubuntu).

Offline

#8 2008-05-13 17:04:28

fifafrazer
Member
Registered: 2008-02-18
Posts: 77

Re: Phoronix Test Suite released and Result collection

Has anyone found a way to get version 0.6 working with Arch. I've just downloaded it, but it gives no output.

Offline

#9 2008-05-14 13:43:16

schivmeister
Developer/TU
From: Singapore
Registered: 2007-05-17
Posts: 971
Website

Re: Phoronix Test Suite released and Result collection

It works. It's a script, so I find no reason why it shouldn't output anything. You will need php package.


I need real, proper pen and paper for this.

Offline

#10 2008-05-14 14:57:34

Mikko777
Member
From: Suomi, Finland
Registered: 2006-10-30
Posts: 837

Re: Phoronix Test Suite released and Result collection

fifafrazer wrote:

Has anyone found a way to get version 0.6 working with Arch. I've just downloaded it, but it gives no output.

I had that same issue also, I tried again with the git ".tar.gz snapshot of the latest Phoronix Test Suite code"
version from here:

http://www.phoronix-test-suite.com/inde … =downloads

Just tested audio encoding again and...

Would you like to save these benchmark results (Y/n)? 
Enter a name to save these results: testi
Enter a unique identifier for distinguishing this series of tests: 1

====================================
LAME MP3 Encoding (Run 1 of 3)
====================================

./lame: line 3: /usr/bin/time: No such file or directory

====================================
LAME MP3 Encoding (Run 2 of 3)
====================================

./lame: line 3: /usr/bin/time: No such file or directory

====================================
LAME MP3 Encoding (Run 3 of 3)
====================================

./lame: line 3: /usr/bin/time: No such file or directory

====================================
LAME MP3 Encoding:


Average: .00 Seconds
====================================

Still no worky, sadly.

Offline

#11 2008-05-18 07:44:48

suolx
Member
From: Finland, Oulu
Registered: 2007-08-06
Posts: 29

Re: Phoronix Test Suite released and Result collection

I got it working. php.ini file needs some tinkering to enable posix commands.
What comes to /usr/bin/time "pacman -S time" does wonders. Theres maybe something else but can't check it right now.

Offline

#12 2008-05-18 11:50:13

Mikko777
Member
From: Suomi, Finland
Registered: 2006-10-30
Posts: 837

Re: Phoronix Test Suite released and Result collection

suolx wrote:

I got it working. php.ini file needs some tinkering to enable posix commands.
What comes to /usr/bin/time "pacman -S time" does wonders. Theres maybe something else but can't check it right now.

Thanks! Didn't realize time was a package roll (thought it used the shell time command).
Anyways after installing time and enabling posix and gd extensions in php.ini it seems to finally work.

Here's a mp3-encode test with Athlonxp 3000+ (not autodetected ^^)

======================================
Phoronix Test Suite v0.7.0 (TRONDHEIM)
System Information
======================================

Hardware:
Processor: Unknown (Total Cores: 0), Motherboard: ASUSTeK A7N8X-E, Chipset: nVidia nForce2 AGP, System Memory: UnknownMB, Disk Space: 0GB, Graphics: ATI RADEON 9600 Series, Screen Resolution: 1680x1050

Software:
OS: , Kernel: 2.6.24-ARCH (i686), X.Org Server: 1.4.0.90, OpenGL: 2.1.7415, Compiler: GCC 4.3.0

[~/bin/phoronix-test-suite]: ./phoronix-test-suite benchmark encode-mp3

Would you like to save these benchmark results (Y/n)? 
Enter a name to save these results: testencodemp3     
Enter a unique identifier for distinguishing this series of tests: 1

====================================
LAME MP3 Encoding (Run 1 of 3)      
====================================

WAV To MP3 Encode Time: 29.79 Seconds

====================================
LAME MP3 Encoding (Run 2 of 3)      
====================================

WAV To MP3 Encode Time: 29.58 Seconds

====================================
LAME MP3 Encoding (Run 3 of 3)      
====================================

WAV To MP3 Encode Time: 29.46 Seconds

====================================
LAME MP3 Encoding:                  

29.79 Seconds
29.58 Seconds
29.46 Seconds

Average: 29.61 Seconds
====================================

Now if someone would test Arch32bit vs Arch64bit it would be interesting cool

Offline

#13 2009-01-09 03:30:05

haukew
Member
From: Hamburg, Germany
Registered: 2007-10-25
Posts: 96
Website

Re: Phoronix Test Suite released and Result collection

Anyways after installing time and enabling posix and gd extensions in php.ini it seems to finally work.

What does this mean exactly?
Which packages need to be installed and how does php.ini have to be modified?

When i start a benchmark it says this:
(for example)


====================================
Unigine Tropics (Run 3 of 3)
====================================

No protocol specified
Engine::init(): clear video settings for "Unknown GPU"
No protocol specified

Unigine fatal error
AppWindow::AppWindow(): can't open display

Loading "/home/hauke/.phoronix-test-suite/installed-tests/unigine-tropics/Unigine_Tropics-1.1/bin/../data/unigine.cfg"...
Loading "libGL.so.1"...
Shutdown

####################################
Unigine Tropics:
1280 x 1024

otocol specified Frames Per Second
otocol specified Frames Per Second
otocol specified Frames Per Second

Average: 0.00 Frames Per Second
####################################

After of course Run 1 and 2 ended the same way...

Starting the test by itself just works. It's definetely a phoronix-error.

Last edited by haukew (2009-01-09 03:31:34)

Offline

#14 2009-01-09 15:40:13

Mikko777
Member
From: Suomi, Finland
Registered: 2006-10-30
Posts: 837

Re: Phoronix Test Suite released and Result collection

haukew wrote:

Anyways after installing time and enabling posix and gd extensions in php.ini it seems to finally work.

What does this mean exactly?
Which packages need to be installed and how does php.ini have to be modified?

1: yaourt -S phoronix-test-suite
2: add 'time' to depends, or install from extra
3: edit /etc/php/php.ini
    - uncomment following extensions:
              - extension=gd.so
              - extension=posix.so
              - extension=curl.so
    - add test-suite path to open_basedir
              example: open_basedir = /srv/http/:/home/:/tmp/:/usr/share/pear/:/usr/share/phoronix-test-suite/
    - allow fileuploads
              - allow_url_fopen = On
              - file_uploads = On
              - allow_url_include = On

4: when installing test suites keep an eye out for other deps pts cannot install by itself

5: make a pts global account and upload results and post links here tongue


Edit: Added some more configuration options by actually readind the _now_ good documentation.
http://www.phoronix-test-suite.com/docu … index.html

Last edited by Mikko777 (2009-01-09 16:11:43)

Offline

#15 2009-01-09 16:28:54

Mikko777
Member
From: Suomi, Finland
Registered: 2006-10-30
Posts: 837

Re: Phoronix Test Suite released and Result collection

Works, although it doesnt detect the hardware info properly it seems.

linky: arch64, 4Gb ddr2 800mhz, raid0, intel quadcore q9550, radeonhd 4850

http://global.phoronix-test-suite.com/i … 3-8474-142

Offline

#16 2009-02-15 21:34:31

Zibi1981
Member
From: Poland
Registered: 2008-01-31
Posts: 471

Re: Phoronix Test Suite released and Result collection

Mikko777 wrote:
haukew wrote:

Anyways after installing time and enabling posix and gd extensions in php.ini it seems to finally work.

What does this mean exactly?
Which packages need to be installed and how does php.ini have to be modified?

1: yaourt -S phoronix-test-suite
2: add 'time' to depends, or install from extra
3: edit /etc/php/php.ini
    - uncomment following extensions:
              - extension=gd.so
              - extension=posix.so
              - extension=curl.so
    - add test-suite path to open_basedir
              example: open_basedir = /srv/http/:/home/:/tmp/:/usr/share/pear/:/usr/share/phoronix-test-suite/
    - allow fileuploads
              - allow_url_fopen = On
              - file_uploads = On
              - allow_url_include = On

4: when installing test suites keep an eye out for other deps pts cannot install by itself

5: make a pts global account and upload results and post links here tongue


Edit: Added some more configuration options by actually readind the _now_ good documentation.
http://www.phoronix-test-suite.com/docu … index.html

I did all that but still cannot make it work sad

zbyszek /usr/share/phoronix-test-suite $  phoronix-test-suite list-tests

====================================
PHORONIX TEST SUITE - WELCOME
====================================

The Phoronix Test Suite is the most comprehensive testing and
benchmarking platform available for Linux and is designed to
carry out tests in a clean, reproducible, and easy-to-use manner.
This software ships with over 70 test profiles and 30 test
suites, but new tests and suites can be easily added through its
XML-based test profile system.

- The Phoronix Test Suite is open-source and licensed under the
GNU GPLv3. However, some tests supported by the PTS are not
open-source. To see the license of tests, run:
phoronix-test-suite list-tests.

- The Phoronix Test Suite contains tests which may stress your
system and in some cases could exhibit stability problems of the
system's hardware or software configuration. The Phoronix Test
Suite is provided WITHOUT ANY WARRANTY. Phoronix Media and
involved parties take no responsibility for misuse of this
software. Use of the Phoronix Test Suite is at your own risk.

- For enterprise support, sponsorship, or other professional
inquiries, contact phoronix@phoronix.com. Community support can
be found in the Phoronix Forums at
http://www.phoronix.com/forums/.

- If you opt to submit your test results to Phoronix Global, the
final results as well as basic hardware and software details
(what is shown in the PTS Results Viewer) will be shared and
publicly accessible through
http://global.phoronix-test-suite.com/.

For more information on the Phoronix Test Suite and its
possibilities, visit http://www.phoronix-test-suite.com/ or view
the included documentation.


Do you agree to these terms and wish to proceed (Y/n)? y


====================================
Phoronix Test Suite - Tests
====================================


zbyszek /usr/share/phoronix-test-suite $

Last edited by Zibi1981 (2009-02-15 21:36:25)


"... being a Linux user is sort of like living in a house inhabited by a large family of carpenters and architects. Every morning when you wake up, the house is a little different. Maybe there is a new turret, or some walls have moved. Or perhaps someone has temporarily removed the floor under your bed."

MSI GT75 Titan 8RG

Offline

#17 2009-03-14 22:41:55

greyhat.goon
Member
From: SF Bay Area
Registered: 2008-05-05
Posts: 57

Re: Phoronix Test Suite released and Result collection

Man, still no luck with getting phoronix test suite going on Arch 64 (or 32 for that matter).  I modified my php.in as described above but still a no go.  I made a post over
on the phoronix forum detailing the problem:

http://phoronix.com/forums/showthread.p … #post66792

Has anyone been able to make PTS work??


Beware of all enterprises that require new clothes....Thoreau

Offline

#18 2009-03-15 08:27:27

Zibi1981
Member
From: Poland
Registered: 2008-01-31
Posts: 471

Re: Phoronix Test Suite released and Result collection

No, still nothing sad


"... being a Linux user is sort of like living in a house inhabited by a large family of carpenters and architects. Every morning when you wake up, the house is a little different. Maybe there is a new turret, or some walls have moved. Or perhaps someone has temporarily removed the floor under your bed."

MSI GT75 Titan 8RG

Offline

#19 2009-03-15 08:39:55

greyhat.goon
Member
From: SF Bay Area
Registered: 2008-05-05
Posts: 57

Re: Phoronix Test Suite released and Result collection

Actually, I got it to work.........mostly.  Some of the tests still don't work for whatever reason, but most of the one's that I've tried do work.  I modified my php.ini file as described above.  In addition, I modified the open_basedir in php.ini as follows.

open_basedir = /srv/http/:/home/:/tmp/:/usr/share/pear/:/usr/share/phoronix-test-suite/:/usr/bin/gcc:/usr/bin/wget:/proc/

I'm attaching my php.ini file for posterity.

[PHP]

;;;;;;;;;;;;;;;;;;;
; About php.ini   ;
;;;;;;;;;;;;;;;;;;;
; This file controls many aspects of PHP's behavior.  In order for PHP to
; read it, it must be named 'php.ini'.  PHP looks for it in the current
; working directory, in the path designated by the environment variable
; PHPRC, and in the path that was defined in compile time (in that order).
; The path in which the php.ini file is looked for can be overridden using
; the -c argument in command line mode.
;
; The syntax of the file is extremely simple.  Whitespace and Lines
; beginning with a semicolon are silently ignored (as you probably guessed).
; Section headers (e.g. [Foo]) are also silently ignored, even though
; they might mean something in the future.
;
; Directives are specified using the following syntax:
; directive = value
; Directive names are *case sensitive* - foo=bar is different from FOO=bar.
;
; The value can be a string, a number, a PHP constant (e.g. E_ALL or M_PI), one
; of the INI constants (On, Off, True, False, Yes, No and None) or an expression
; (e.g. E_ALL & ~E_NOTICE), or a quoted string ("foo").
;
; Expressions in the INI file are limited to bitwise operators and parentheses:
; |        bitwise OR
; &        bitwise AND
; ~        bitwise NOT
; !        boolean NOT
;
; Boolean flags can be turned on using the values 1, On, True or Yes.
; They can be turned off using the values 0, Off, False or No.
;
; An empty string can be denoted by simply not writing anything after the equal
; sign, or by using the None keyword:
;
;  foo =         ; sets foo to an empty string
;  foo = none    ; sets foo to an empty string
;  foo = "none"  ; sets foo to the string 'none'
;
; If you use constants in your value, and these constants belong to a
; dynamically loaded extension (either a PHP extension or a Zend extension),
; you may only use these constants *after* the line that loads the extension.
;
;
;;;;;;;;;;;;;;;;;;;
; About this file ;
;;;;;;;;;;;;;;;;;;;
; This is the recommended, PHP 5-style version of the php.ini-dist file.  It
; sets some non standard settings, that make PHP more efficient, more secure,
; and encourage cleaner coding.
;
; The price is that with these settings, PHP may be incompatible with some
; applications, and sometimes, more difficult to develop with.  Using this
; file is warmly recommended for production sites.  As all of the changes from
; the standard settings are thoroughly documented, you can go over each one,
; and decide whether you want to use it or not.
;
; For general information about the php.ini file, please consult the php.ini-dist
; file, included in your PHP distribution.
;
; This file is different from the php.ini-dist file in the fact that it features
; different values for several directives, in order to improve performance, while
; possibly breaking compatibility with the standard out-of-the-box behavior of
; PHP.  Please make sure you read what's different, and modify your scripts
; accordingly, if you decide to use this file instead.
;
; - register_long_arrays = Off     [Performance]
;     Disables registration of the older (and deprecated) long predefined array
;     variables ($HTTP_*_VARS).  Instead, use the superglobals that were
;     introduced in PHP 4.1.0
; - display_errors = Off           [Security]
;     With this directive set to off, errors that occur during the execution of
;     scripts will no longer be displayed as a part of the script output, and thus,
;     will no longer be exposed to remote users.  With some errors, the error message
;     content may expose information about your script, web server, or database
;     server that may be exploitable for hacking.  Production sites should have this
;     directive set to off.
; - log_errors = On                [Security]
;     This directive complements the above one.  Any errors that occur during the
;     execution of your script will be logged (typically, to your server's error log,
;     but can be configured in several ways).  Along with setting display_errors to off,
;     this setup gives you the ability to fully understand what may have gone wrong,
;     without exposing any sensitive information to remote users.
; - output_buffering = 4096        [Performance]
;     Set a 4KB output buffer.  Enabling output buffering typically results in less
;     writes, and sometimes less packets sent on the wire, which can often lead to
;     better performance.  The gain this directive actually yields greatly depends
;     on which Web server you're working with, and what kind of scripts you're using.
; - register_argc_argv = Off       [Performance]
;     Disables registration of the somewhat redundant $argv and $argc global
;     variables.
; - magic_quotes_gpc = Off         [Performance]
;     Input data is no longer escaped with slashes so that it can be sent into
;     SQL databases without further manipulation.  Instead, you should use the
;     database vendor specific escape string function on each input element you
;     wish to send to a database.
; - variables_order = "GPCS"       [Performance]
;     The environment variables are not hashed into the $_ENV.  To access
;     environment variables, you can use getenv() instead.
; - error_reporting = E_ALL        [Code Cleanliness, Security(?)]
;     By default, PHP suppresses errors of type E_NOTICE.  These error messages
;     are emitted for non-critical errors, but that could be a symptom of a bigger
;     problem.  Most notably, this will cause error messages about the use
;     of uninitialized variables to be displayed.
; - allow_call_time_pass_reference = Off     [Code cleanliness]
;     It's not possible to decide to force a variable to be passed by reference
;     when calling a function.  The PHP 4 style to do this is by making the
;     function require the relevant argument by reference.
; - short_open_tag = Off           [Portability]
;     Using short tags is discouraged when developing code meant for redistribution
;     since short tags may not be supported on the target server.

;;;;;;;;;;;;;;;;;;;;
; Language Options ;
;;;;;;;;;;;;;;;;;;;;

; Enable the PHP scripting language engine under Apache.
engine = On

; Enable compatibility mode with Zend Engine 1 (PHP 4.x)
zend.ze1_compatibility_mode = Off

; Allow the <? tag.  Otherwise, only <?php and <script> tags are recognized.
; NOTE: Using short tags should be avoided when developing applications or
; libraries that are meant for redistribution, or deployment on PHP
; servers which are not under your control, because short tags may not
; be supported on the target server. For portable, redistributable code,
; be sure not to use short tags.
short_open_tag = Off

; Allow ASP-style <% %> tags.
asp_tags = Off

; The number of significant digits displayed in floating point numbers.
precision    =  14

; Enforce year 2000 compliance (will cause problems with non-compliant browsers)
y2k_compliance = On

; Output buffering allows you to send header lines (including cookies) even
; after you send body content, at the price of slowing PHP's output layer a
; bit.  You can enable output buffering during runtime by calling the output
; buffering functions.  You can also enable output buffering for all files by
; setting this directive to On.  If you wish to limit the size of the buffer
; to a certain size - you can use a maximum number of bytes instead of 'On', as
; a value for this directive (e.g., output_buffering=4096).
output_buffering = 4096

; You can redirect all of the output of your scripts to a function.  For
; example, if you set output_handler to "mb_output_handler", character
; encoding will be transparently converted to the specified encoding.
; Setting any output handler automatically turns on output buffering.
; Note: People who wrote portable scripts should not depend on this ini
;       directive. Instead, explicitly set the output handler using ob_start().
;       Using this ini directive may cause problems unless you know what script
;       is doing.
; Note: You cannot use both "mb_output_handler" with "ob_iconv_handler"
;       and you cannot use both "ob_gzhandler" and "zlib.output_compression".
; Note: output_handler must be empty if this is set 'On' !!!!
;       Instead you must use zlib.output_handler.
;output_handler =

; Transparent output compression using the zlib library
; Valid values for this option are 'off', 'on', or a specific buffer size
; to be used for compression (default is 4KB)
; Note: Resulting chunk size may vary due to nature of compression. PHP
;       outputs chunks that are few hundreds bytes each as a result of
;       compression. If you prefer a larger chunk size for better
;       performance, enable output_buffering in addition.
; Note: You need to use zlib.output_handler instead of the standard
;       output_handler, or otherwise the output will be corrupted.
zlib.output_compression = Off
;zlib.output_compression_level = -1

; You cannot specify additional output handlers if zlib.output_compression
; is activated here. This setting does the same as output_handler but in
; a different order.
;zlib.output_handler =

; Implicit flush tells PHP to tell the output layer to flush itself
; automatically after every output block.  This is equivalent to calling the
; PHP function flush() after each and every call to print() or echo() and each
; and every HTML block.  Turning this option on has serious performance
; implications and is generally recommended for debugging purposes only.
implicit_flush = Off

; The unserialize callback function will be called (with the undefined class'
; name as parameter), if the unserializer finds an undefined class
; which should be instantiated.
; A warning appears if the specified function is not defined, or if the
; function doesn't include/implement the missing class.
; So only set this entry, if you really want to implement such a
; callback-function.
unserialize_callback_func=

; When floats & doubles are serialized store serialize_precision significant
; digits after the floating point. The default value ensures that when floats
; are decoded with unserialize, the data will remain the same.
serialize_precision = 100

; Whether to enable the ability to force arguments to be passed by reference
; at function call time.  This method is deprecated and is likely to be
; unsupported in future versions of PHP/Zend.  The encouraged method of
; specifying which arguments should be passed by reference is in the function
; declaration.  You're encouraged to try and turn this option Off and make
; sure your scripts work properly with it in order to ensure they will work
; with future versions of the language (you will receive a warning each time
; you use this feature, and the argument will be passed by value instead of by
; reference).
allow_call_time_pass_reference = Off

;
; Safe Mode
;
safe_mode = Off

; By default, Safe Mode does a UID compare check when
; opening files. If you want to relax this to a GID compare,
; then turn on safe_mode_gid.
safe_mode_gid = Off

; When safe_mode is on, UID/GID checks are bypassed when
; including files from this directory and its subdirectories.
; (directory must also be in include_path or full path must
; be used when including)
safe_mode_include_dir =

; When safe_mode is on, only executables located in the safe_mode_exec_dir
; will be allowed to be executed via the exec family of functions.
safe_mode_exec_dir =

; Setting certain environment variables may be a potential security breach.
; This directive contains a comma-delimited list of prefixes.  In Safe Mode,
; the user may only alter environment variables whose names begin with the
; prefixes supplied here.  By default, users will only be able to set
; environment variables that begin with PHP_ (e.g. PHP_FOO=BAR).
;
; Note:  If this directive is empty, PHP will let the user modify ANY
; environment variable!
safe_mode_allowed_env_vars = PHP_

; This directive contains a comma-delimited list of environment variables that
; the end user won't be able to change using putenv().  These variables will be
; protected even if safe_mode_allowed_env_vars is set to allow to change them.
safe_mode_protected_env_vars = LD_LIBRARY_PATH

; open_basedir, if set, limits all file operations to the defined directory
; and below.  This directive makes most sense if used in a per-directory
; or per-virtualhost web server configuration file. This directive is
; *NOT* affected by whether Safe Mode is turned On or Off.
open_basedir = /srv/http/:/home/:/tmp/:/usr/share/pear/:/usr/share/phoronix-test-suite/:/usr/bin/gcc:/usr/bin/wget:/proc/

; This directive allows you to disable certain functions for security reasons.
; It receives a comma-delimited list of function names. This directive is
; *NOT* affected by whether Safe Mode is turned On or Off.
disable_functions =

; This directive allows you to disable certain classes for security reasons.
; It receives a comma-delimited list of class names. This directive is
; *NOT* affected by whether Safe Mode is turned On or Off.
disable_classes =

; Colors for Syntax Highlighting mode.  Anything that's acceptable in
; <span style="color: ???????"> would work.
;highlight.string  = #DD0000
;highlight.comment = #FF9900
;highlight.keyword = #007700
;highlight.bg      = #FFFFFF
;highlight.default = #0000BB
;highlight.html    = #000000

; If enabled, the request will be allowed to complete even if the user aborts
; the request. Consider enabling it if executing long request, which may end up
; being interrupted by the user or a browser timing out.
; ignore_user_abort = On

; Determines the size of the realpath cache to be used by PHP. This value should
; be increased on systems where PHP opens many files to reflect the quantity of
; the file operations performed.
; realpath_cache_size=16k

; Duration of time, in seconds for which to cache realpath information for a given
; file or directory. For systems with rarely changing files, consider increasing this
; value.
; realpath_cache_ttl=120

;
; Misc
;
; Decides whether PHP may expose the fact that it is installed on the server
; (e.g. by adding its signature to the Web server header).  It is no security
; threat in any way, but it makes it possible to determine whether you use PHP
; on your server or not.
expose_php = Off


;;;;;;;;;;;;;;;;;;;
; Resource Limits ;
;;;;;;;;;;;;;;;;;;;

max_execution_time = 30     ; Maximum execution time of each script, in seconds
max_input_time = 60    ; Maximum amount of time each script may spend parsing request data
;max_input_nesting_level = 64 ; Maximum input variable nesting level
memory_limit = 32M      ; Maximum amount of memory a script may consume (32MB)


;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; Error handling and logging ;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

; error_reporting is a bit-field.  Or each number up to get desired error
; reporting level
; E_ALL             - All errors and warnings (doesn't include E_STRICT)
; E_ERROR           - fatal run-time errors
; E_RECOVERABLE_ERROR  - almost fatal run-time errors
; E_WARNING         - run-time warnings (non-fatal errors)
; E_PARSE           - compile-time parse errors
; E_NOTICE          - run-time notices (these are warnings which often result
;                     from a bug in your code, but it's possible that it was
;                     intentional (e.g., using an uninitialized variable and
;                     relying on the fact it's automatically initialized to an
;                     empty string)
; E_STRICT          - run-time notices, enable to have PHP suggest changes
;                     to your code which will ensure the best interoperability
;                     and forward compatibility of your code
; E_CORE_ERROR      - fatal errors that occur during PHP's initial startup
; E_CORE_WARNING    - warnings (non-fatal errors) that occur during PHP's
;                     initial startup
; E_COMPILE_ERROR   - fatal compile-time errors
; E_COMPILE_WARNING - compile-time warnings (non-fatal errors)
; E_USER_ERROR      - user-generated error message
; E_USER_WARNING    - user-generated warning message
; E_USER_NOTICE     - user-generated notice message
;
; Examples:
;
;   - Show all errors, except for notices and coding standards warnings
;
;error_reporting = E_ALL & ~E_NOTICE
;
;   - Show all errors, except for notices
;
;error_reporting = E_ALL & ~E_NOTICE | E_STRICT
;
;   - Show only errors
;
;error_reporting = E_COMPILE_ERROR|E_RECOVERABLE_ERROR|E_ERROR|E_CORE_ERROR
;
;   - Show all errors, except coding standards warnings
;
error_reporting  =  E_ALL

; Print out errors (as a part of the output).  For production web sites,
; you're strongly encouraged to turn this feature off, and use error logging
; instead (see below).  Keeping display_errors enabled on a production web site
; may reveal security information to end users, such as file paths on your Web
; server, your database schema or other information.
;
; possible values for display_errors:
;
; Off          - Do not display any errors 
; stderr       - Display errors to STDERR (affects only CGI/CLI binaries!)
; On or stdout - Display errors to STDOUT (default)
;
; To output errors to STDERR with CGI/CLI:
;display_errors = "stderr"
;
; Default
;
display_errors = Off

; Even when display_errors is on, errors that occur during PHP's startup
; sequence are not displayed.  It's strongly recommended to keep
; display_startup_errors off, except for when debugging.
display_startup_errors = Off

; Log errors into a log file (server-specific log, stderr, or error_log (below))
; As stated above, you're strongly advised to use error logging in place of
; error displaying on production web sites.
log_errors = On

; Set maximum length of log_errors. In error_log information about the source is
; added. The default is 1024 and 0 allows to not apply any maximum length at all.
log_errors_max_len = 1024

; Do not log repeated messages. Repeated errors must occur in same file on same
; line unless ignore_repeated_source is set true.
ignore_repeated_errors = Off

; Ignore source of message when ignoring repeated messages. When this setting
; is On you will not log errors with repeated messages from different files or
; source lines.
ignore_repeated_source = Off

; If this parameter is set to Off, then memory leaks will not be shown (on
; stdout or in the log). This has only effect in a debug compile, and if
; error reporting includes E_WARNING in the allowed list
report_memleaks = Off

;report_zend_debug = 0

; Store the last error/warning message in $php_errormsg (boolean).
track_errors = Off

; Turn off normal error reporting and emit XML-RPC error XML
;xmlrpc_errors = 0
; An XML-RPC faultCode
;xmlrpc_error_number = 0

; Disable the inclusion of HTML tags in error messages.
; Note: Never use this feature for production boxes.
;html_errors = Off

; If html_errors is set On PHP produces clickable error messages that direct
; to a page describing the error or function causing the error in detail.
; You can download a copy of the PHP manual from http://www.php.net/docs.php
; and change docref_root to the base URL of your local copy including the
; leading '/'. You must also specify the file extension being used including
; the dot.
; Note: Never use this feature for production boxes.
;docref_root = "/phpmanual/"
;docref_ext = .html

; String to output before an error message.
;error_prepend_string = "<font color=#ff0000>"

; String to output after an error message.
;error_append_string = "</font>"

; Log errors to specified file.
;error_log = filename

; Log errors to syslog.
error_log = syslog


;;;;;;;;;;;;;;;;;
; Data Handling ;
;;;;;;;;;;;;;;;;;
;
; Note - track_vars is ALWAYS enabled as of PHP 4.0.3

; The separator used in PHP generated URLs to separate arguments.
; Default is "&".
;arg_separator.output = "&"

; List of separator(s) used by PHP to parse input URLs into variables.
; Default is "&".
; NOTE: Every character in this directive is considered as separator!
;arg_separator.input = ";&"

; This directive describes the order in which PHP registers GET, POST, Cookie,
; Environment and Built-in variables (G, P, C, E & S respectively, often
; referred to as EGPCS or GPC).  Registration is done from left to right, newer
; values override older values.
variables_order = "GPCS"

; Whether or not to register the EGPCS variables as global variables.  You may
; want to turn this off if you don't want to clutter your scripts' global scope
; with user data.  This makes most sense when coupled with track_vars - in which
; case you can access all of the GPC variables through the $HTTP_*_VARS[],
; variables.
;
; You should do your best to write your scripts so that they do not require
; register_globals to be on;  Using form variables as globals can easily lead
; to possible security problems, if the code is not very well thought of.
register_globals = Off

; Whether or not to register the old-style input arrays, HTTP_GET_VARS
; and friends.  If you're not using them, it's recommended to turn them off,
; for performance reasons.
register_long_arrays = Off

; This directive tells PHP whether to declare the argv&argc variables (that
; would contain the GET information).  If you don't use these variables, you
; should turn it off for increased performance.
register_argc_argv = Off

; When enabled, the SERVER and ENV variables are created when they're first
; used (Just In Time) instead of when the script starts. If these variables
; are not used within a script, having this directive on will result in a
; performance gain. The PHP directives register_globals, register_long_arrays,
; and register_argc_argv must be disabled for this directive to have any affect.
auto_globals_jit = On

; Maximum size of POST data that PHP will accept.
post_max_size = 8M

; Magic quotes
;

; Magic quotes for incoming GET/POST/Cookie data.
magic_quotes_gpc = Off

; Magic quotes for runtime-generated data, e.g. data from SQL, from exec(), etc.
magic_quotes_runtime = Off

; Use Sybase-style magic quotes (escape ' with '' instead of \').
magic_quotes_sybase = Off

; Automatically add files before or after any PHP document.
auto_prepend_file =
auto_append_file =

; As of 4.0b4, PHP always outputs a character encoding by default in
; the Content-type: header.  To disable sending of the charset, simply
; set it to be empty.
;
; PHP's built-in default is text/html
default_mimetype = "text/html"
;default_charset = "iso-8859-1"

; Always populate the $HTTP_RAW_POST_DATA variable.
;always_populate_raw_post_data = On


;;;;;;;;;;;;;;;;;;;;;;;;;
; Paths and Directories ;
;;;;;;;;;;;;;;;;;;;;;;;;;

; UNIX: "/path1:/path2"
include_path = ".:/usr/share/pear"

; The root of the PHP pages, used only if nonempty.
; if PHP was not compiled with FORCE_REDIRECT, you SHOULD set doc_root
; if you are running php as a CGI under any web server (other than IIS)
; see documentation for security issues.  The alternate is to use the
; cgi.force_redirect configuration below
doc_root =

; The directory under which PHP opens the script using /~username used only
; if nonempty.
user_dir =

; Directory in which the loadable extensions (modules) reside.
extension_dir = "/usr/lib/php/20060613/"

; Whether or not to enable the dl() function.  The dl() function does NOT work
; properly in multithreaded servers, such as IIS or Zeus, and is automatically
; disabled on them.
enable_dl = Off

; cgi.force_redirect is necessary to provide security running PHP as a CGI under
; most web servers.  Left undefined, PHP turns this on by default.  You can
; turn it off here AT YOUR OWN RISK
; **You CAN safely turn this off for IIS, in fact, you MUST.**
; cgi.force_redirect = 1

; if cgi.nph is enabled it will force cgi to always sent Status: 200 with
; every request.
; cgi.nph = 1

; if cgi.force_redirect is turned on, and you are not running under Apache or Netscape
; (iPlanet) web servers, you MAY need to set an environment variable name that PHP
; will look for to know it is OK to continue execution.  Setting this variable MAY
; cause security issues, KNOW WHAT YOU ARE DOING FIRST.
; cgi.redirect_status_env = ;

; cgi.fix_pathinfo provides *real* PATH_INFO/PATH_TRANSLATED support for CGI.  PHP's
; previous behaviour was to set PATH_TRANSLATED to SCRIPT_FILENAME, and to not grok
; what PATH_INFO is.  For more information on PATH_INFO, see the cgi specs.  Setting
; this to 1 will cause PHP CGI to fix it's paths to conform to the spec.  A setting
; of zero causes PHP to behave as before.  Default is 1.  You should fix your scripts
; to use SCRIPT_FILENAME rather than PATH_TRANSLATED.
; cgi.fix_pathinfo=1

; FastCGI under IIS (on WINNT based OS) supports the ability to impersonate
; security tokens of the calling client.  This allows IIS to define the
; security context that the request runs under.  mod_fastcgi under Apache
; does not currently support this feature (03/17/2002)
; Set to 1 if running under IIS.  Default is zero.
; fastcgi.impersonate = 1;

; Disable logging through FastCGI connection
; fastcgi.logging = 0

; cgi.rfc2616_headers configuration option tells PHP what type of headers to
; use when sending HTTP response code. If it's set 0 PHP sends Status: header that
; is supported by Apache. When this option is set to 1 PHP will send
; RFC2616 compliant header.
; Default is zero.
;cgi.rfc2616_headers = 0


;;;;;;;;;;;;;;;;
; File Uploads ;
;;;;;;;;;;;;;;;;

; Whether to allow HTTP file uploads.
file_uploads = On

; Temporary directory for HTTP uploaded files (will use system default if not
; specified).
;upload_tmp_dir =

; Maximum allowed size for uploaded files.
upload_max_filesize = 2M


;;;;;;;;;;;;;;;;;;
; Fopen wrappers ;
;;;;;;;;;;;;;;;;;;

; Whether to allow the treatment of URLs (like http:// or ftp://) as files.
allow_url_fopen = On

; Whether to allow include/require to open URLs (like http:// or ftp://) as files.
allow_url_include = On

; Define the anonymous ftp password (your email address)
;from="john@doe.com"

; Define the User-Agent string
; user_agent="PHP"

; Default timeout for socket based streams (seconds)
default_socket_timeout = 60

;;;;;;;;;;;;;;;;;;;;;;
; Dynamic Extensions ;
;;;;;;;;;;;;;;;;;;;;;;
;
; If you wish to have an extension loaded automatically, use the following
; syntax:
;
;   extension=modulename.extension
;
; For example, under UNIX:
;
;   extension=msql.so
;
; Note that it should be the name of the module only; no directory information
; needs to go here.  Specify the location of the extension with the
; extension_dir directive above.

;;;;;;;;;;;;;;;;;;;
; Module Settings ;
;;;;;;;;;;;;;;;;;;;

[Date]
; Defines the default timezone used by the date functions
;date.timezone =

;date.default_latitude = 31.7667
;date.default_longitude = 35.2333

;date.sunrise_zenith = 90.583333
;date.sunset_zenith = 90.583333

[filter]
;filter.default = unsafe_raw
;filter.default_flags =

[iconv]
;iconv.input_encoding = ISO-8859-1
;iconv.internal_encoding = ISO-8859-1
;iconv.output_encoding = ISO-8859-1

[sqlite]
;sqlite.assoc_case = 0

[Pcre]
;PCRE library backtracking limit.
;pcre.backtrack_limit=100000

;PCRE library recursion limit.
;Please note that if you set this value to a high number you may consume all
;the available process stack and eventually crash PHP (due to reaching the
;stack size limit imposed by the Operating System).
;pcre.recursion_limit=100000

[Syslog]
; Whether or not to define the various syslog variables (e.g. $LOG_PID,
; $LOG_CRON, etc.).  Turning it off is a good idea performance-wise.  In
; runtime, you can define these variables by calling define_syslog_variables().
define_syslog_variables  = Off

[mail function]
; For Unix only.  You may supply arguments as well (default: "sendmail -t -i").
;sendmail_path =

; Force the addition of the specified parameters to be passed as extra parameters
; to the sendmail binary. These parameters will always replace the value of
; the 5th parameter to mail(), even in safe mode.
;mail.force_extra_parameters =

[SQL]
sql.safe_mode = Off

[ODBC]
;odbc.default_db    =  Not yet implemented
;odbc.default_user  =  Not yet implemented
;odbc.default_pw    =  Not yet implemented

; Allow or prevent persistent links.
odbc.allow_persistent = On

; Check that a connection is still valid before reuse.
odbc.check_persistent = On

; Maximum number of persistent links.  -1 means no limit.
odbc.max_persistent = -1

; Maximum number of links (persistent + non-persistent).  -1 means no limit.
odbc.max_links = -1

; Handling of LONG fields.  Returns number of bytes to variables.  0 means
; passthru.
odbc.defaultlrl = 4096

; Handling of binary data.  0 means passthru, 1 return as is, 2 convert to char.
; See the documentation on odbc_binmode and odbc_longreadlen for an explanation
; of uodbc.defaultlrl and uodbc.defaultbinmode
odbc.defaultbinmode = 1

[MySQL]
; Allow or prevent persistent links.
mysql.allow_persistent = On

; Maximum number of persistent links.  -1 means no limit.
mysql.max_persistent = -1

; Maximum number of links (persistent + non-persistent).  -1 means no limit.
mysql.max_links = -1

; Default port number for mysql_connect().  If unset, mysql_connect() will use
; the $MYSQL_TCP_PORT or the mysql-tcp entry in /etc/services or the
; compile-time value defined MYSQL_PORT (in that order).
mysql.default_port =

; Default socket name for local MySQL connects.  If empty, uses the built-in
; MySQL defaults.
mysql.default_socket =

; Default host for mysql_connect() (doesn't apply in safe mode).
mysql.default_host =

; Default user for mysql_connect() (doesn't apply in safe mode).
mysql.default_user =

; Default password for mysql_connect() (doesn't apply in safe mode).
; Note that this is generally a *bad* idea to store passwords in this file.
; *Any* user with PHP access can run 'echo get_cfg_var("mysql.default_password")
; and reveal this password!  And of course, any users with read access to this
; file will be able to reveal the password as well.
mysql.default_password =

; Maximum time (in seconds) for connect timeout. -1 means no limit
mysql.connect_timeout = 60

; Trace mode. When trace_mode is active (=On), warnings for table/index scans and
; SQL-Errors will be displayed.
mysql.trace_mode = Off

[MySQLi]

; Maximum number of links.  -1 means no limit.
mysqli.max_links = -1

; Default port number for mysqli_connect().  If unset, mysqli_connect() will use
; the $MYSQL_TCP_PORT or the mysql-tcp entry in /etc/services or the
; compile-time value defined MYSQL_PORT (in that order).
mysqli.default_port = 3306

; Default socket name for local MySQL connects.  If empty, uses the built-in
; MySQL defaults.
mysqli.default_socket =

; Default host for mysql_connect() (doesn't apply in safe mode).
mysqli.default_host =

; Default user for mysql_connect() (doesn't apply in safe mode).
mysqli.default_user =

; Default password for mysqli_connect() (doesn't apply in safe mode).
; Note that this is generally a *bad* idea to store passwords in this file.
; *Any* user with PHP access can run 'echo get_cfg_var("mysqli.default_pw")
; and reveal this password!  And of course, any users with read access to this
; file will be able to reveal the password as well.
mysqli.default_pw =

; Allow or prevent reconnect
mysqli.reconnect = Off

[mSQL]
; Allow or prevent persistent links.
msql.allow_persistent = On

; Maximum number of persistent links.  -1 means no limit.
msql.max_persistent = -1

; Maximum number of links (persistent+non persistent).  -1 means no limit.
msql.max_links = -1

[OCI8]
; enables privileged connections using external credentials (OCI_SYSOPER, OCI_SYSDBA)
;oci8.privileged_connect = Off

; Connection: The maximum number of persistent OCI8 connections per
; process. Using -1 means no limit.
;oci8.max_persistent = -1

; Connection: The maximum number of seconds a process is allowed to
; maintain an idle persistent connection. Using -1 means idle
; persistent connections will be maintained forever.
;oci8.persistent_timeout = -1

; Connection: The number of seconds that must pass before issuing a
; ping during oci_pconnect() to check the connection validity. When
; set to 0, each oci_pconnect() will cause a ping. Using -1 disables
; pings completely.
;oci8.ping_interval = 60

; Tuning: This option enables statement caching, and specifies how
; many statements to cache. Using 0 disables statement caching.
;oci8.statement_cache_size = 20

; Tuning: Enables statement prefetching and sets the default number of
; rows that will be fetched automatically after statement execution.
;oci8.default_prefetch = 10

; Compatibility. Using On means oci_close() will not close
; oci_connect() and oci_new_connect() connections.
;oci8.old_oci_close_semantics = Off

[PostgresSQL]
; Allow or prevent persistent links.
pgsql.allow_persistent = On

; Detect broken persistent links always with pg_pconnect().
; Auto reset feature requires a little overheads.
pgsql.auto_reset_persistent = Off

; Maximum number of persistent links.  -1 means no limit.
pgsql.max_persistent = -1

; Maximum number of links (persistent+non persistent).  -1 means no limit.
pgsql.max_links = -1

; Ignore PostgreSQL backends Notice message or not.
; Notice message logging require a little overheads.
pgsql.ignore_notice = 0

; Log PostgreSQL backends Notice message or not.
; Unless pgsql.ignore_notice=0, module cannot log notice message.
pgsql.log_notice = 0

[Sybase]
; Allow or prevent persistent links.
sybase.allow_persistent = On

; Maximum number of persistent links.  -1 means no limit.
sybase.max_persistent = -1

; Maximum number of links (persistent + non-persistent).  -1 means no limit.
sybase.max_links = -1

;sybase.interface_file = "/usr/sybase/interfaces"

; Minimum error severity to display.
sybase.min_error_severity = 10

; Minimum message severity to display.
sybase.min_message_severity = 10

; Compatibility mode with old versions of PHP 3.0.
; If on, this will cause PHP to automatically assign types to results according
; to their Sybase type, instead of treating them all as strings.  This
; compatibility mode will probably not stay around forever, so try applying
; whatever necessary changes to your code, and turn it off.
sybase.compatability_mode = Off

[Sybase-CT]
; Allow or prevent persistent links.
sybct.allow_persistent = On

; Maximum number of persistent links.  -1 means no limit.
sybct.max_persistent = -1

; Maximum number of links (persistent + non-persistent).  -1 means no limit.
sybct.max_links = -1

; Minimum server message severity to display.
sybct.min_server_severity = 10

; Minimum client message severity to display.
sybct.min_client_severity = 10

[bcmath]
; Number of decimal digits for all bcmath functions.
bcmath.scale = 0

[browscap]
;browscap = extra/browscap.ini

[Informix]
; Default host for ifx_connect() (doesn't apply in safe mode).
ifx.default_host =

; Default user for ifx_connect() (doesn't apply in safe mode).
ifx.default_user =

; Default password for ifx_connect() (doesn't apply in safe mode).
ifx.default_password =

; Allow or prevent persistent links.
ifx.allow_persistent = On

; Maximum number of persistent links.  -1 means no limit.
ifx.max_persistent = -1

; Maximum number of links (persistent + non-persistent).  -1 means no limit.
ifx.max_links = -1

; If on, select statements return the contents of a text blob instead of its id.
ifx.textasvarchar = 0

; If on, select statements return the contents of a byte blob instead of its id.
ifx.byteasvarchar = 0

; Trailing blanks are stripped from fixed-length char columns.  May help the
; life of Informix SE users.
ifx.charasvarchar = 0

; If on, the contents of text and byte blobs are dumped to a file instead of
; keeping them in memory.
ifx.blobinfile = 0

; NULL's are returned as empty strings, unless this is set to 1.  In that case,
; NULL's are returned as string 'NULL'.
ifx.nullformat = 0

[Session]
; Handler used to store/retrieve data.
session.save_handler = files

; Argument passed to save_handler.  In the case of files, this is the path
; where data files are stored.
;
; As of PHP 4.0.1, you can define the path as:
;
;     session.save_path = "N;/path"
;
; where N is an integer.  Instead of storing all the session files in
; /path, what this will do is use subdirectories N-levels deep, and
; store the session data in those directories.  This is useful if you
; or your OS have problems with lots of files in one directory, and is
; a more efficient layout for servers that handle lots of sessions.
;
; NOTE 1: PHP will not create this directory structure automatically.
;         You can use the script in the ext/session dir for that purpose.
; NOTE 2: See the section on garbage collection below if you choose to
;         use subdirectories for session storage
;
; The file storage module creates files using mode 600 by default.
; You can change that by using
;
;     session.save_path = "N;MODE;/path"
;
; where MODE is the octal representation of the mode. Note that this
; does not overwrite the process's umask.
session.save_path = "/tmp"

; Whether to use cookies.
session.use_cookies = 1

;session.cookie_secure =

; This option enables administrators to make their users invulnerable to
; attacks which involve passing session ids in URLs; defaults to 0.
; session.use_only_cookies = 1

; Name of the session (used as cookie name).
session.name = PHPSESSID

; Initialize session on request startup.
session.auto_start = 0

; Lifetime in seconds of cookie or, if 0, until browser is restarted.
session.cookie_lifetime = 0

; The path for which the cookie is valid.
session.cookie_path = /

; The domain for which the cookie is valid.
session.cookie_domain =

; Whether or not to add the httpOnly flag to the cookie, which makes it inaccessible to browser scripting languages such as JavaScript.
session.cookie_httponly =

; Handler used to serialize data.  php is the standard serializer of PHP.
session.serialize_handler = php

; Define the probability that the 'garbage collection' process is started
; on every session initialization.
; The probability is calculated by using gc_probability/gc_divisor,
; e.g. 1/100 means there is a 1% chance that the GC process starts
; on each request.

session.gc_probability = 1
session.gc_divisor     = 1000

; After this number of seconds, stored data will be seen as 'garbage' and
; cleaned up by the garbage collection process.
session.gc_maxlifetime = 1440

; NOTE: If you are using the subdirectory option for storing session files
;       (see session.save_path above), then garbage collection does *not*
;       happen automatically.  You will need to do your own garbage
;       collection through a shell script, cron entry, or some other method.
;       For example, the following script would is the equivalent of
;       setting session.gc_maxlifetime to 1440 (1440 seconds = 24 minutes):
;          cd /path/to/sessions; find -cmin +24 | xargs rm

; PHP 4.2 and less have an undocumented feature/bug that allows you to
; to initialize a session variable in the global scope, albeit register_globals
; is disabled.  PHP 4.3 and later will warn you, if this feature is used.
; You can disable the feature and the warning separately. At this time,
; the warning is only displayed, if bug_compat_42 is enabled.

session.bug_compat_42 = 0
session.bug_compat_warn = 1

; Check HTTP Referer to invalidate externally stored URLs containing ids.
; HTTP_REFERER has to contain this substring for the session to be
; considered as valid.
session.referer_check =

; How many bytes to read from the file.
session.entropy_length = 0

; Specified here to create the session id.
session.entropy_file =

;session.entropy_length = 16

;session.entropy_file = /dev/urandom

; Set to {nocache,private,public,} to determine HTTP caching aspects
; or leave this empty to avoid sending anti-caching headers.
session.cache_limiter = nocache

; Document expires after n minutes.
session.cache_expire = 180

; trans sid support is disabled by default.
; Use of trans sid may risk your users security.
; Use this option with caution.
; - User may send URL contains active session ID
;   to other person via. email/irc/etc.
; - URL that contains active session ID may be stored
;   in publically accessible computer.
; - User may access your site with the same session ID
;   always using URL stored in browser's history or bookmarks.
session.use_trans_sid = 0

; Select a hash function
; 0: MD5   (128 bits)
; 1: SHA-1 (160 bits)
session.hash_function = 0

; Define how many bits are stored in each character when converting
; the binary hash data to something readable.
;
; 4 bits: 0-9, a-f
; 5 bits: 0-9, a-v
; 6 bits: 0-9, a-z, A-Z, "-", ","
session.hash_bits_per_character = 5

; The URL rewriter will look for URLs in a defined set of HTML tags.
; form/fieldset are special; if you include them here, the rewriter will
; add a hidden <input> field with the info which is otherwise appended
; to URLs.  If you want XHTML conformity, remove the form entry.
; Note that all valid entries require a "=", even if no value follows.
url_rewriter.tags = "a=href,area=href,frame=src,input=src,form=fakeentry"

[MSSQL]
; Allow or prevent persistent links.
mssql.allow_persistent = On

; Maximum number of persistent links.  -1 means no limit.
mssql.max_persistent = -1

; Maximum number of links (persistent+non persistent).  -1 means no limit.
mssql.max_links = -1

; Minimum error severity to display.
mssql.min_error_severity = 10

; Minimum message severity to display.
mssql.min_message_severity = 10

; Compatibility mode with old versions of PHP 3.0.
mssql.compatability_mode = Off

; Connect timeout
;mssql.connect_timeout = 5

; Query timeout
;mssql.timeout = 60

; Valid range 0 - 2147483647.  Default = 4096.
;mssql.textlimit = 4096

; Valid range 0 - 2147483647.  Default = 4096.
;mssql.textsize = 4096

; Limits the number of records in each batch.  0 = all records in one batch.
;mssql.batchsize = 0

; Specify how datetime and datetim4 columns are returned
; On => Returns data converted to SQL server settings
; Off => Returns values as YYYY-MM-DD hh:mm:ss
;mssql.datetimeconvert = On

; Use NT authentication when connecting to the server
mssql.secure_connection = Off

; Specify max number of processes. -1 = library default
; msdlib defaults to 25
; FreeTDS defaults to 4096
;mssql.max_procs = -1

; Specify client character set.
; If empty or not set the client charset from freetds.comf is used
; This is only used when compiled with FreeTDS
;mssql.charset = "ISO-8859-1"

[Assertion]
; Assert(expr); active by default.
;assert.active = On

; Issue a PHP warning for each failed assertion.
;assert.warning = On

; Don't bail out by default.
;assert.bail = Off

; User-function to be called if an assertion fails.
;assert.callback = 0

; Eval the expression with current error_reporting().  Set to true if you want
; error_reporting(0) around the eval().
;assert.quiet_eval = 0

[COM]
; path to a file containing GUIDs, IIDs or filenames of files with TypeLibs
;com.typelib_file =
; allow Distributed-COM calls
;com.allow_dcom = true
; autoregister constants of a components typlib on com_load()
;com.autoregister_typelib = true
; register constants casesensitive
;com.autoregister_casesensitive = false
; show warnings on duplicate constant registrations
;com.autoregister_verbose = true

[mbstring]
; language for internal character representation.
;mbstring.language = Japanese

; internal/script encoding.
; Some encoding cannot work as internal encoding.
; (e.g. SJIS, BIG5, ISO-2022-*)
;mbstring.internal_encoding = EUC-JP

; http input encoding.
;mbstring.http_input = auto

; http output encoding. mb_output_handler must be
; registered as output buffer to function
;mbstring.http_output = SJIS

; enable automatic encoding translation according to
; mbstring.internal_encoding setting. Input chars are
; converted to internal encoding by setting this to On.
; Note: Do _not_ use automatic encoding translation for
;       portable libs/applications.
;mbstring.encoding_translation = Off

; automatic encoding detection order.
; auto means
;mbstring.detect_order = auto

; substitute_character used when character cannot be converted
; one from another
;mbstring.substitute_character = none;

; overload(replace) single byte functions by mbstring functions.
; mail(), ereg(), etc are overloaded by mb_send_mail(), mb_ereg(),
; etc. Possible values are 0,1,2,4 or combination of them.
; For example, 7 for overload everything.
; 0: No overload
; 1: Overload mail() function
; 2: Overload str*() functions
; 4: Overload ereg*() functions
;mbstring.func_overload = 0

; enable strict encoding detection.
;mbstring.strict_encoding = Off

[FrontBase]
;fbsql.allow_persistent = On
;fbsql.autocommit = On
;fbsql.show_timestamp_decimals = Off
;fbsql.default_database =
;fbsql.default_database_password =
;fbsql.default_host =
;fbsql.default_password =
;fbsql.default_user = "_SYSTEM"
;fbsql.generate_warnings = Off
;fbsql.max_connections = 128
;fbsql.max_links = 128
;fbsql.max_persistent = -1
;fbsql.max_results = 128

[gd]
; Tell the jpeg decode to libjpeg warnings and try to create
; a gd image. The warning will then be displayed as notices
; disabled by default
;gd.jpeg_ignore_warning = 0

[exif]
; Exif UNICODE user comments are handled as UCS-2BE/UCS-2LE and JIS as JIS.
; With mbstring support this will automatically be converted into the encoding
; given by corresponding encode setting. When empty mbstring.internal_encoding
; is used. For the decode settings you can distinguish between motorola and
; intel byte order. A decode setting cannot be empty.
;exif.encode_unicode = ISO-8859-15
;exif.decode_unicode_motorola = UCS-2BE
;exif.decode_unicode_intel    = UCS-2LE
;exif.encode_jis =
;exif.decode_jis_motorola = JIS
;exif.decode_jis_intel    = JIS

[Tidy]
; The path to a default tidy configuration file to use when using tidy
;tidy.default_config = /usr/local/lib/php/default.tcfg

; Should tidy clean and repair output automatically?
; WARNING: Do not use this option if you are generating non-html content
; such as dynamic images
tidy.clean_output = Off

[soap]
; Enables or disables WSDL caching feature.
soap.wsdl_cache_enabled=1
; Sets the directory name where SOAP extension will put cache files.
soap.wsdl_cache_dir="/tmp"
; (time to live) Sets the number of second while cached file will be used
; instead of original one.
soap.wsdl_cache_ttl=86400


; available extensions
;
;extension=bcmath.so
;extension=bz2.so
;extension=calendar.so
extension=curl.so
;extension=dba.so
;extension=dbase.so
;extension=exif.so
;extension=ftp.so
extension=gd.so
extension=gettext.so
;extension=gmp.so
;extension=iconv.so
;extension=imap.so
;extension=json.so
;extension=ldap.so
;extension=mcrypt.so
;extension=mhash.so
;extension=mime_magic.so
;extension=mysql.so
;extension=mysqli.so
;extension=ncurses.so
;extension=odbc.so
;extension=openssl.so
;extension=pdo.so
;extension=pdo_mysql.so
;extension=pdo_odbc.so
;extension=pdo_pgsql.so
;extension=pdo_sqlite.so
;extension=pgsql.so
extension=posix.so
;extension=pspell.so
extension=session.so
;extension=shmop.so
;extension=snmp.so
;extension=soap.so
;extension=sockets.so
;extension=sqlite.so
;extension=sysvmsg.so
;extension=sysvsem.so
;extension=sysvshm.so
;extension=tidy.so
;extension=xmlrpc.so
;extension=xsl.so
;extension=zip.so
extension=zlib.so


; Local Variables:
; tab-width: 4
; End:

Beware of all enterprises that require new clothes....Thoreau

Offline

#20 2009-07-23 11:36:25

Jaguar07
Member
Registered: 2009-07-23
Posts: 5

Re: Phoronix Test Suite released and Result collection

PASHA

So what if I have background processes running.

IT is GooD to be the King

http://global.phoronix-test-suite.com/? … 0585-24030

Why YES, yes that is a Dual Xeon based Quad that I had for breakfast at Phoronix today.

I have to admit Archlinux was a royal pain in the Ascii to install but the spoils were worth the efforts.
It reminds me a lot of the older slackware distros.  Obviously, the benchmark results, show there's a huge benefit if performance is your goal.

The php.ini info helped me considerably in posting my lastest phoronix results.  Thank you to everyone that contributed to that. : D

Offline

#21 2009-07-23 12:11:09

eldragon
Member
From: Buenos Aires
Registered: 2008-11-18
Posts: 1,028

Re: Phoronix Test Suite released and Result collection

Jaguar07 wrote:

PASHA

So what if I have background processes running.

IT is GooD to be the King

http://global.phoronix-test-suite.com/? … 0585-24030

Why YES, yes that is a Dual Xeon based Quad that I had for breakfast at Phoronix today.

I have to admit Archlinux was a royal pain in the Ascii to install but the spoils were worth the efforts.
It reminds me a lot of the older slackware distros.  Obviously, the benchmark results, show there's a huge benefit if performance is your goal.

The php.ini info helped me considerably in posting my lastest phoronix results.  Thank you to everyone that contributed to that. : D

im no benchmark wizzard, but isnt using the same hardware on all tests a requirement for software benchmarks?

anyway, feels good to be king big_smile

Offline

#22 2009-07-24 14:08:01

Jaguar07
Member
Registered: 2009-07-23
Posts: 5

Re: Phoronix Test Suite released and Result collection

im no benchmark wizzard, but isnt using the same hardware on all tests a requirement for software benchmarks?

That depends.

In the Benchmark results I posted a link to, the hardware is identical for the two E8400 systems.  One has F11 x64, The other has Archlinux x64.

When you compare hardware to hardware(or software to software) it would be ideal to have the exact same software(or hardware) on all systems.  That works wonderfully well in theory and in a test lab.   Practical application tends to dictate otherwise.  If you have the budget, I will be more than happy to prove this theorem in a Lab environment on your time.

This is one simple example of where the experience of years of testing vs. the theory of testing makes a HUGE difference:

If my webserver serves up 100,000,000 hits per hour and the Dell R9000 crashes, the lesson may become a permanent fatal error.  Especially if your gross sales are in the $1-$2 Million per hour range or you are creating a high profile site for a fortune 500 corporation.

At Shopping.com, at the time the 3rd largest e-commerce site and a division of Compaq, I proved this theory over and over again to representatives from Compaq HQ; Alta Vista; Intel; and Microsoft.



There are always a finite number of tests.  The real question is, are you willing to actually perform the due dilligence to find that number? - Jeffrey R. Evans aka Jaguar07

Offline

#23 2009-07-24 14:34:11

eldragon
Member
From: Buenos Aires
Registered: 2008-11-18
Posts: 1,028

Re: Phoronix Test Suite released and Result collection

Jaguar07 wrote:

im no benchmark wizzard, but isnt using the same hardware on all tests a requirement for software benchmarks?

That depends.

In the Benchmark results I posted a link to, the hardware is identical for the two E8400 systems.  One has F11 x64, The other has Archlinux x64.

When you compare hardware to hardware(or software to software) it would be ideal to have the exact same software(or hardware) on all systems.  That works wonderfully well in theory and in a test lab.   Practical application tends to dictate otherwise.  If you have the budget, I will be more than happy to prove this theorem in a Lab environment on your time.

This is one simple example of where the experience of years of testing vs. the theory of testing makes a HUGE difference:

If my webserver serves up 100,000,000 hits per hour and the Dell R9000 crashes, the lesson may become a permanent fatal error.  Especially if your gross sales are in the $1-$2 Million per hour range or you are creating a high profile site for a fortune 500 corporation.

At Shopping.com, at the time the 3rd largest e-commerce site and a division of Compaq, I proved this theory over and over again to representatives from Compaq HQ; Alta Vista; Intel; and Microsoft.



There are always a finite number of tests.  The real question is, are you willing to actually perform the due dilligence to find that number? - Jeffrey R. Evans aka Jaguar07

then the best benchmark would be a brady family head snapshot after a month of usage.. the biggest smile would mean the best setup.

if you are posting numbers, do it correctly.using the almighty car analogy, what you did is like doing gas efficiency test with different cars....

its like the glxgears test. we all know its not a valid benchmark, yet people use it as first approach to see how fast their graphics card can potentially be. (of if its working correctly for that matter).

so, if you are testing hardware, use the same software, and if you are testing software (which is what you apparently tried to do) use the same hardware.

it does not matter how useless the compiling apache benchmark is, it will be even more useless if you do it wrong.

Offline

#24 2009-07-24 14:53:40

Jaguar07
Member
Registered: 2009-07-23
Posts: 5

Re: Phoronix Test Suite released and Result collection

Gas efficiency tests with different models of cars are VALID.  Even if Ford doesn't appreciate the fact that Honda wins VS. Ford at the time.

Offline

#25 2009-07-24 15:02:25

eldragon
Member
From: Buenos Aires
Registered: 2008-11-18
Posts: 1,028

Re: Phoronix Test Suite released and Result collection

Jaguar07 wrote:

Gas efficiency tests with different models of cars are VALID.  Even if Ford doesn't appreciate the fact that Honda wins VS. Ford at the time.

you are benchmarking cars, im benchmarking gasoline

Offline

Board footer

Powered by FluxBB