please send the binaries
Thans
Original message from: Bug Database <[EMAIL PROTECTED]>
>
>ID: 10577
>Updated by: andi
>Reported By: [EMAIL PROTECTED]
>Old-Status: Open
>Status: Feedback
>Bug Type: Program Execution
>PHP Version: 4.0.5
>Assigned To:
>Comments:
>
>This should be fixed in the latest CVS. If you can try it or the
latest snapshot from snaps.php.net that would be good. If not, we can
send you binaries of the latest CVS.
>
>Previous Comments:
>---------------------------------------------------------------------
------
>
>[2001-05-01 08:10:55] [EMAIL PROTECTED]
>i've just downloaded today the latest release
>and the following code still returns only 0;
>
>------------------
>$test = system("cmd.exe /c dir", $return_value);
>echo $test;
>echo $return_value;
>-----------
>retuns: 0
>
>Why?
>
>
>here is my INI in case
>-------------------------------------
>[PHP]
>; $Id: php.ini-dist,v 1.73.2.2 2001/04/22 11:58:49 phanto Exp $
>
>;;;;;;;;;;;;;;;;;;;
>; About this file ;
>;;;;;;;;;;;;;;;;;;;
>; 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).
>; Under Windows, the compile-time path is the Windows directory. The
>; path in which the php.ini file is looked for can be overriden 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.
>;
>; All the values in the php.ini-dist file correspond to the builtin
>; defaults (that is, if no php.ini is used, or if you delete these
lines,
>; the builtin defaults will be identical).
>
>
>;;;;;;;;;;;;;;;;;;;;
>; Language Options ;
>;;;;;;;;;;;;;;;;;;;;
>
>; Enable the PHP scripting language engine under Apache.
>engine = On
>
>; Allow the <? tag. Otherwise, only <?php and <script> tags are
recognized.
>short_open_tag = On
>
>; 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 = Off
>
>; 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.
>output_buffering = Off
>
>; You can redirect all of the output of your scripts to a function.
For
>; example, if you set output_handler to "ob_gzhandler", output will
be
>; transparently compressed for browsers that support gzip or deflate
encoding.
>; Setting an output handler automatically turns on output buffering.
>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)
>zlib.output_compression = Off
>
>; 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
>
>; 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 = On
>
>
>;
>; Safe Mode
>;
>safe_mode = Off
>
>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
>
>; This directive allows you to disable certain functions for security
reasons.
>; It receives a comma-deliminated list of function names. This
directive is
>; *NOT* affected by whether Safe Mode is turned On or Off.
>disable_functions =
>
>; Colors for Syntax Highlighting mode. Anything that's acceptable in
>; <font color="??????"> would work.
>highlight.string = #CC0000
>highlight.comment = #FF9900
>highlight.keyword = #006600
>highlight.bg = #FFFFFF
>highlight.default = #0000CC
>highlight.html = #000000
>
>
>;
>; 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 = On
>
>
>;;;;;;;;;;;;;;;;;;;
>; Resource Limits ;
>;;;;;;;;;;;;;;;;;;;
>
>max_execution_time = 30 ; Maximum execution time of each script,
in seconds
__________________________________________________________________
Get your free Australian email account at http://www.start.com.au
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
