Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

error_log(3) [php man page]

ERROR_LOG(3)								 1							      ERROR_LOG(3)

error_log - Send an error message to the defined error handling routines

SYNOPSIS
bool error_log (string $message, [int $message_type], [string $destination], [string $extra_headers]) DESCRIPTION
Sends an error message to the web server's error log or to a file. PARAMETERS
o $message - The error message that should be logged. o $message_type - Says where the error should go. The possible message types are as follows: error_log(3) log types +--+---------------------------------------------------+ |0 | | | | | | | $message is sent to PHP's system logger, using | | | the Operating System's system logging mechanism | | | or a file, depending on what the error_log con- | | | figuration directive is set to. This is the | | | default option. | | | | |1 | | | | | | | $message is sent by email to the address in the | | | $destination parameter. This is the only message | | | type where the fourth parameter, $extra_headers | | | is used. | | | | |2 | | | | | | | No longer an option. | | | | |3 | | | | | | | $message is appended to the file $destination. A | | | newline is not automatically added to the end of | | | the $message string. | | | | |4 | | | | | | | $message is sent directly to the SAPI logging | | | handler. | | | | +--+---------------------------------------------------+ o $destination - The destination. Its meaning depends on the $message_type parameter as described above. o $extra_headers - The extra headers. It's used when the $message_type parameter is set to 1. This message type uses the same internal function as mail(3) does. RETURN VALUES
Returns TRUE on success or FALSE on failure. NOTES
Warning error_log(3) is not binary safe. $message will be truncated by null character. Tip $message should not contain null character. Note that $message may be sent to file, mail, syslog, etc. Use appropriate conver- sion/escape function, base64_encode(3), rawurlencode(3) or addslashes(3) before calling error_log(3). EXAMPLES
Example #1 error_log(3) examples <?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"); ?> CHANGELOG
+--------+---------------------------------------------------+ |Version | | | | | | | Description | | | | +--------+---------------------------------------------------+ | 5.2.7 | | | | | | | The possible value of 4 was added to $mes- | | | sage_type. | | | | +--------+---------------------------------------------------+ PHP Documentation Group ERROR_LOG(3)

Check Out this Related Man Page

lucancel(1M)						  System Administration Commands					      lucancel(1M)

NAME
lucancel - cancel a scheduled Live Upgrade copy/create procedure SYNOPSIS
/usr/sbin/lucancel [-l error_log] [-o outfile] [-X] DESCRIPTION
The lucancel command is part of a suite of commands that make up the Live Upgrade feature of the Solaris operating environment. See live_upgrade(5) for a description of the Live Upgrade feature. The lucancel command cancels a boot environment (BE) creation or upgrade that was scheduled in the FMLI-based interface, lu(1M), or the repopulation of a BE, scheduled with lumake(1M). lucancel does not cancel a job that is active (that is, is in the process of creation or repopulation). The lucancel command requires root privileges. OPTIONS
The lucancel command has the following options: -l error_log Error and status messages are sent to error_log, in addition to where they are sent in your current environment. -o outfile All command output is sent to outfile, in addition to where it is sent in your current environment. -X Enable XML output. Characteristics of XML are defined in DTD, in /usr/share/lib/xml/dtd/lu_cli.dtd.<num>, where <num> is the version number of the DTD file. EXIT STATUS
The following exit values are returned: 0 Successful completion. >0 An error occurred. FILES
/etc/lutab list of BEs on the system ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWluu | +-----------------------------+-----------------------------+ SEE ALSO
lu(1M), luactivate(1M), lucompare(1M), lucreate(1M), lucurr(1M), ludelete(1M), ludesc(1M), lufslist(1M), lumake(1M), lumount(1M), lure- name(1M), lustatus(1M), luupgrade(1M), lutab(4), attributes(5), live_upgrade(5) SunOS 5.10 21 Dec 2001 lucancel(1M)
Man Page