At 6:19 PM -0400 7/12/06, Michael B Allen wrote:
On Wed, 12 Jul 2006 22:44:23 +0100
Stut [EMAIL PROTECTED] wrote:
Michael B Allen wrote:
Thanks for the tip dipshit.
Maybe I'm in a sensitive mood, but that was uncalled for. Michael, meet
/dev/null, I hope you live happily ever after.
Oh,
tedd wrote:
At 6:19 PM -0400 7/12/06, Michael B Allen wrote:
On Wed, 12 Jul 2006 22:44:23 +0100
Stut [EMAIL PROTECTED] wrote:
Michael B Allen wrote:
Thanks for the tip dipshit.
Maybe I'm in a sensitive mood, but that was uncalled for. Michael, meet
/dev/null, I hope you live happily ever
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael B Allen wrote:
What is the standard method of logging debug info? Should I just fopen
a file for append and write the message or is there a facility provided?
http://php.net/syslog or use a file. There are also various JS-based
solutions
http://pear.php.net/package/Log/ works well for me. Supports writing
messages to files, to a separate window via JavaScript, probably syslog as
well as a few others.
-Original Message-
From: Michael B Allen [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 12, 2006 2:02 PM
To:
I wrote my own, very simple, very easy. I think the code is in the
archive somewhere. Otheres have written similar functions.
CODE +++
function logError ($logentry, $lgname) {
// simple function to log errors to text/log file.
$logfile =
Michael B Allen wrote:
What is the standard method of logging debug info? Should I just fopen
a file for append and write the message or is there a facility provided?
there is also error_log() (and the 'error_log' ini setting)
- I abuse it for debugging now and again.
Mike
--
PHP
Ahh yes I do that as well, I knew there was another other then syslog.
On 7/12/06, Jochem Maas [EMAIL PROTECTED] wrote:
Michael B Allen wrote:
What is the standard method of logging debug info? Should I just fopen
a file for append and write the message or is there a facility provided?
there
On Wed, 12 Jul 2006 19:13:53 +0100
Stut [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael B Allen wrote:
What is the standard method of logging debug info? Should I just fopen
a file for append and write the message or is there a facility provided?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael B Allen wrote:
On Wed, 12 Jul 2006 19:13:53 +0100
Stut [EMAIL PROTECTED] wrote:
Michael B Allen wrote:
What is the standard method of logging debug info? Should I just fopen
a file for append and write the message or is there a facility
On Wed, 12 Jul 2006 21:13:31 +0100
Stut [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael B Allen wrote:
On Wed, 12 Jul 2006 19:13:53 +0100
Stut [EMAIL PROTECTED] wrote:
Michael B Allen wrote:
What is the standard method of logging debug info? Should I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael B Allen wrote:
Thanks for the tip dipshit.
Maybe I'm in a sensitive mood, but that was uncalled for. Michael, meet
/dev/null, I hope you live happily ever after.
- -Stut
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.2 (GNU/Linux)
On Wed, 12 Jul 2006 22:44:23 +0100
Stut [EMAIL PROTECTED] wrote:
Michael B Allen wrote:
Thanks for the tip dipshit.
Maybe I'm in a sensitive mood, but that was uncalled for. Michael, meet
/dev/null, I hope you live happily ever after.
Oh, no. What am I going to do now? You're like The Man
Michael B Allen wrote:
On Wed, 12 Jul 2006 22:44:23 +0100
Stut [EMAIL PROTECTED] wrote:
Michael B Allen wrote:
Thanks for the tip dipshit.
Maybe I'm in a sensitive mood, but that was uncalled for. Michael, meet
/dev/null, I hope you live happily ever after.
Oh, no. What am I going to do
13 matches
Mail list logo
