Lines Matching refs:be
36 + Where a configuration setting may be set
96 PHP source code and binary distributions for Windows can be found at
192 with various options, like which extensions will be enabled. Do a
218 If you instead choose php.ini-production, be certain to read the list
224 added this for you, but be sure to check.
241 source, this can be done with:
268 stage. It isn't supposed to. It will be created.)
356 ("Group daemon" is also very common) PHP will not be able to open
381 installation options for Apache may be found there.
383 The most recent version of Apache HTTP Server may be obtained from
389 be replaced with the specific version of Apache being used.
422 various options, like which extensions will be enabled. Run
447 If you instead choose php.ini-production, be certain to read the
452 already added this for you, but be sure to check.
465 and .phtml files to be executed as PHP, but nothing else, we'd use
470 And to allow .phps files to be handled by the php source filter,
475 mod_rewrite may be used To allow any arbitrary .php file to be
480 The php source filter should not be enabled on production systems,
494 Apache may be built multithreaded by selecting the worker MPM, rather
500 This should not be undertaken without being aware of the consequences
512 support threads. In this case, PHP should also be built with
514 all extensions will be available. The recommended setup is to build
561 reached. The directives "min-procs" and "max-procs" should generally be
565 will be multiplied PHP_FCGI_CHILDREN (2 min-procs * 16 children gives
608 Fastcgi instances can be spawned on multiple remote machines in order
684 will be something like /opt/netscape/suitespot/bin/libphp4.so. You
724 5. Setup of authentication: PHP authentication cannot be used with any
814 But be warned: Support for nsapi_virtual() is EXPERIMENTAL!!!
820 By default, PHP is built as both a CLI and CGI program, which can be
846 SERVER_SOFTWARE. Everything else should be treated as 'vendor
878 modules, and each can be installed and removed independently from the
879 others. The files you need can be found on your OpenBSD CD or on the
922 session files to be stored, or use an alternative session backend.
923 In addition, database sockets need to be placed inside the jail or
926 will need to be moved into /var/www/etc. The OpenBSD PEAR package
931 be installed. If you do not wish to use some of the font features
996 should be reported to the Debian team unless they can be reproduced
1006 First, note that other related packages may be desired like
1017 its dependencies, and then activate it. Apache should be restarted in
1027 very likely that additional modules will be desired, such as MySQL,
1028 cURL, GD, etc. These may also be installed via the apt-get command.
1054 file, which on Debian may be /etc/apache2/apache2.conf or similar.
1057 undefined, be sure that the appropriate ini file is being loaded
1136 on legacy machines may be /etc/httpd/httpd.conf.
1145 above files should be replaced or commented out.
1180 but this can be set to anything in httpd.conf. Alternatively, the
1235 To be useful, a shared extension must be built, installed, and loaded.
1238 load them. Extensions can be loaded by adding an extension directive.
1260 the » pecl command. Specific revisions may also be specified.
1262 be seen at » http://svn.php.net/viewvc/pecl/. To download straight
1263 from SVN, the following sequence of commands may be used:
1300 you may still be able to find one in PECL. The PHP Extension Community
1361 error can be read directly on screen.
1374 the right settings. Again, phpinfo() can be of great help.
1386 extname.so into your extension_dir. extname.so may then be loaded via
1402 is required for the changes to be picked up.
1408 Sometimes, using the pecl installer is not an option. This could be
1409 because you're behind a firewall, or it could be because the extension
1430 (like RPM's) are used, be sure to also install the appropriate devel
1450 be queried anytime by running php-config with the -h switch:
1517 libraries uses --enable. To be sure, run the following after buildconf:
1543 may be able to help you. You should check out the archive first, in
1551 If you want to get help on the mailing list, please try to be precise
1563 chances are it won't be fixed. You can report bugs using the
1580 * Where a configuration setting may be set
1597 * As of PHP 5.2.0, the location of the php.ini file can be set for
1603 IniFilePath in any of these keys, the first one found will be used
1615 name can be determined with php_sapi_name().
1634 ; Boolean values can be set to either:
1667 be recognized in .user.ini-style INI files.
1681 Where a configuration setting may be set
1683 These modes determine when and where a PHP directive may or may not be
1685 For example, some settings may be set within a PHP script using
1689 it may not be set using ini_set(). However, the display_errors
1690 directive is PHP_INI_ALL therefore it may be set anywhere, including
1696 PHP_INI_USER Entry can be set in user scripts (like with ini_set()) or
1697 in the Windows registry. Since PHP 5.3, entry can be set in .user.ini
1698 PHP_INI_PERDIR Entry can be set in php.ini, .htaccess, httpd.conf or
1700 PHP_INI_SYSTEM Entry can be set in php.ini or httpd.conf
1701 PHP_INI_ALL Entry can be set anywhere
1720 Sets the value of the specified directive. Can be used only with
1725 below) should be used instead.
1728 Used to set a boolean configuration directive. Can be used only
1732 Sets the value of the specified directive. This can not be used
1734 can not be overridden by .htaccess or ini_set(). To clear a
1738 Used to set a boolean configuration directive. This can not be
1740 php_admin_flag can not be overridden by .htaccess or ini_set().
1758 constants can be used in php.ini
1762 When running PHP on Windows, the configuration values can be modified
1766 configuration values for the directory c:\inetpub\wwwroot would be
1768 Values\c\inetpub\wwwroot. The settings for the directory would be
1773 PHP_INI_USER can be set this way, PHP_INI_PERDIR values can not.
1799 2. Unix/Windows: Where should my php.ini file be located?
1823 the following error: Security Alert! PHP CGI cannot be accessed
1852 Unix/Windows: Where should my php.ini file be located?
1853 By default on Unix it should be in /usr/local/lib which is
1895 should be submitted to » http://bugs.php.net/
1948 error message will be displayed which will give you a clue as to
1949 what needs to be done next. If you get a screen full of HTML
1951 working, and your problem may be related to your server
1978 running, then a suitable error message will be displayed which
1979 will give you a clue as to what needs to be done next. If you
1984 script via the browser again. If it still fails then it could be
2011 following error: Security Alert! PHP CGI cannot be accessed
2014 to 1 so be sure the directive isn't commented out (with a ;).
2023 To be sure your php.ini is being read by PHP, make a call to
2024 phpinfo(). Near the top, there will be a listing called
2032 then be sure to restart your web server after making changes to
2114 Proper response status can be sent with header(). If only GET
2115 and POST methods should be handled, it can be achieved with this
