# redirect STDERR to log file open(SAVESTDERR, ">&STDERR") or die "Can't save STDERR: $!\n"; open(STDERR, ">$logfile") or die "Can't open STDERR to $logfile", "$!\n"; $|=1; Blah Blah blah
open(STDERR, ">&SAVESTDERR"); # Close log file and restore STDERR -----Original Message----- From: Campbell Simpson [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 14, 2005 10:40 PM To: [EMAIL PROTECTED] Subject: perl-ldap Hi Graham I'm currently making use of your great perl LDAP module through a radius server written in perl called Radiator (http://www.open.com.au/ radiator/) so that I can use the radius server to authenticate users against an LDAP directory. One issue I've encountered is the way that your perl module logs when using the debug flag. You direct the debug output to STDERR. This makes it a little difficult to log this debug information to a log file as you really need to run Radiator from the command line to see the LDAP debug messages. I've hacked your perl module very slightly to direct this debug output to a file with some time stamps. It would be nice if maybe in a future release you could look at how you could pass this debug information back to the controlling perl script so it could log it by what ever means it wants. I'm more of a perl hacker than a perl developer so I haven't tried to figure out how to do this myself. Kind regards Campbell Simpson "This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002."
