Carl Scarlett wrote: > [EMAIL PROTECTED] wrote: > [snip] > >>I think the only way is a hard way... In such situations I put the >>following line into PHP scripts: >> >>syslog(LOG_MAIL|LOG_NOTICE, "Stepped into script.php"); >> >>Then you've the chance to track down where the problem arises (messagages >>were written into syslog/mail.log). Probably that may help ;-) > > > I don't know much about php, but I assume that this command simply prints > a message into the mail.log file?
If you are not working on a production machine, simple echo commands are another option - they will put info to the screen instead. Their usefulness can be less exact and introduce other problems depending on where they are used, but they are generally the first line of debugging in most cases due to their convenience. -paul ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf -- squirrelmail-users mailing list Posting Guidelines: http://squirrelmail.org/wiki/wiki.php?MailingListPostingGuidelines List Address: [email protected] List Archives: http://news.gmane.org/thread.php?group=gmane.mail.squirrelmail.user List Archives: http://sourceforge.net/mailarchive/forum.php?forum_id=2995 List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
