php-doc-en/reference/errorfunc/functions/error-log.xml

<?xml version="1.0" encoding="utf-8"?>
<!-- $Revision$ -->
<refentry xml:id="function.error-log" xmlns="http://docbook.org/ns/docbook">
 <refnamediv>
  <refname>error_log</refname>
  <refpurpose>Send an error message to the defined error handling routines</refpurpose>
 </refnamediv>

 <refsect1 role="description">
  &reftitle.description;
  <methodsynopsis>
   <type>bool</type><methodname>error_log</methodname>
   <methodparam><type>string</type><parameter>message</parameter></methodparam>
   <methodparam choice="opt"><type>int</type><parameter>message_type</parameter><initializer>0</initializer></methodparam>
   <methodparam choice="opt"><type>string</type><parameter>destination</parameter></methodparam>
   <methodparam choice="opt"><type>string</type><parameter>extra_headers</parameter></methodparam>
  </methodsynopsis>
  <para>
   Sends an error message to the web server's error log or to a file.
  </para>
 </refsect1>

 <refsect1 role="parameters">
  &reftitle.parameters;
  <para>
   <variablelist>
    <varlistentry>
     <term><parameter>message</parameter></term>
     <listitem>
      <para>
       The error message that should be logged.
      </para>
     </listitem>
    </varlistentry>
    <varlistentry>
     <term><parameter>message_type</parameter></term>
     <listitem>
      <para>
       Says where the error should go. The possible message types are as 
       follows:
      </para>
      <para>
       <table>
        <title><function>error_log</function> log types</title>
        <tgroup cols="2">
         <tbody>
          <row>
           <entry>0</entry>
           <entry>
            <parameter>message</parameter> is sent to PHP's system logger, using
            the Operating System's system logging mechanism or a file, depending
            on what the <link linkend="ini.error-log">error_log</link>
            configuration directive is set to.  This is the default option.
           </entry>
          </row>
          <row>
           <entry>1</entry>
           <entry>
            <parameter>message</parameter> is sent by email to the address in
            the <parameter>destination</parameter> parameter.  This is the only
            message type where the fourth parameter,
            <parameter>extra_headers</parameter> is used.
           </entry>
          </row>
          <row>
           <entry>2</entry>
           <entry>
            No longer an option.
           </entry>
          </row>
          <row>
           <entry>3</entry>
           <entry>
            <parameter>message</parameter> is appended to the file
            <parameter>destination</parameter>. A newline is not automatically 
            added to the end of the <parameter>message</parameter> string.
           </entry>
          </row>
          <row>
           <entry>4</entry>
           <entry>
           <parameter>message</parameter> is sent directly to the SAPI logging
           handler.
           </entry>
          </row>
         </tbody>
        </tgroup>
       </table>
      </para>
     </listitem>
    </varlistentry>
    <varlistentry>
     <term><parameter>destination</parameter></term>
     <listitem>
      <para>
       The destination. Its meaning depends on the 
       <parameter>message_type</parameter> parameter as described above.
      </para>
     </listitem>
    </varlistentry>
    <varlistentry>
     <term><parameter>extra_headers</parameter></term>
     <listitem>
      <para>
       The extra headers. It's used when the <parameter>message_type</parameter>
       parameter is set to <literal>1</literal>.
       This message type uses the same internal function as 
       <function>mail</function> does.
      </para>
     </listitem>
    </varlistentry>
   </variablelist>
  </para>
 </refsect1>

 <refsect1 role="returnvalues">
  &reftitle.returnvalues;
  <para>
   &return.success;
  </para>
 </refsect1>

 <refsect1 role="notes">
  &reftitle.notes;
  <warning>
   <simpara>
    <function>error_log</function> is not binary safe. <parameter>message</parameter> will be truncated by null character.
   </simpara>
  </warning>
  <tip>
   <simpara>
    <parameter>message</parameter> should not contain null character. Note that <parameter>message</parameter> may be sent to file, mail, syslog, etc. Use appropriate conversion/escape function, <function>base64_encode</function>, <function>rawurlencode</function> or <function>addslashes</function> before calling <function>error_log</function>.
   </simpara>
  </tip>
 </refsect1>

 <refsect1 role="examples">
  &reftitle.examples;
  <para>
   <example role="php">
    <title><function>error_log</function> examples</title>
    <programlisting role="php">
<![CDATA[
<?php
// Send notification through the server log if we can not
// connect to the database.
if (!Ora_Logon($username, $password)) {
    error_log("Oracle database not available!", 0);
}

// Notify administrator by email if we run out of FOO
if (!($foo = allocate_new_foo())) {
    error_log("Big trouble, we're all out of FOOs!", 1,
               "operator@example.com");
}

// another way to call error_log():
error_log("You messed up!", 3, "/var/tmp/my-errors.log");
?>
]]>
    </programlisting>
   </example>
  </para>
 </refsect1>

</refentry>

<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-omittag:t
sgml-shorttag:t
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:1
sgml-indent-data:t
indent-tabs-mode:nil
sgml-parent-document:nil
sgml-default-dtd-file:"~/.phpdoc/manual.ced"
sgml-exposed-tags:nil
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
End:
vim600: syn=xml fen fdm=syntax fdl=2 si
vim: et tw=78 syn=sgml
vi: ts=1 sw=1
-->