<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7226.0">
<TITLE>[rt-users] logging</TITLE>
</HEAD>
<BODY>
<DIV id=idOWAReplyText62458 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>Luke,</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>This may seem like an obvious answer, but
it was what did it for me: Check permissions on the $LogDir directory to
make sure the web server has write permission and make sure you stop and start
the web server.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>BenR</FONT></DIV></DIV>
<DIV dir=ltr><BR>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> rt-users-bounces@lists.bestpractical.com
on behalf of Luke Vanderfluit<BR><B>Sent:</B> Tue 28/03/2006 2:46
PM<BR><B>To:</B> RT users<BR><B>Subject:</B> [rt-users]
logging<BR></FONT><BR></DIV>
<DIV>
<P><FONT size=2>Hi.<BR><BR>I have the following lines in my
RT_SiteConfig.pm<BR><BR>/~~~~~~~~~~~~~~~~~~~~~~~~~~~~<BR># Mail loops will
generate a critical log message.<BR>Set($LogToSyslog ,
'alert');<BR>Set($LogToScreen ,
undef); <BR>Set($LogToFile ,
'alert');<BR>Set($LogDir, '/usr/local/rt3/var/log');<BR>Set($LogToFileNamed ,
"rt3.log"); #log to rt.log<BR><BR>@LogToSyslogConf = ( socket
=> 'inet' );<BR>\_____________________________<BR><BR>In other words I want
to log to the rt3.log file with 'alert' message level.<BR><BR>I don't get any
output in that file, though, no matter what operations I<BR>carry out in
RT.<BR>Is there something that I need to change in Log::Dispatch?<BR><BR>Any
hints on getting logging to rt3.log working?<BR><BR>Thanks.<BR>Kind
regards.<BR><BR>--<BR>Luke<BR><BR>_______________________________________________<BR><A
href="http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users">http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users</A><BR><BR>Community
help: <A
href="http://wiki.bestpractical.com">http://wiki.bestpractical.com</A><BR>Commercial
support: sales@bestpractical.com<BR><BR><BR>Discover RT's hidden secrets with RT
Essentials from O'Reilly Media.<BR>Buy a copy at <A
href="http://rtbook.bestpractical.com">http://rtbook.bestpractical.com</A><BR><BR><BR>We're
hiring! Come hack Perl for Best Practical: <A
href="http://bestpractical.com/about/jobs.html">http://bestpractical.com/about/jobs.html</A><BR></FONT></P></DIV>
<pre>............................................................................................................................
This email (including all attachments) is intended solely for the named addressee. It is confidential and may contain legally privileged information. If you receive it in error, please let us know by reply email, do not disclose any information contained in it, delete it from your system and destroy any copies. This email is also subject to copyright. No part of it should be reproduced, adapted or transmitted without the written consent of the copyright owner. Emails may be interfered with, may contain computer viruses or other defects and may not be successfully replicated on other systems.
We give no warranties in relation to these matters. If you have any doubts about the authenticity of an email purportedly sent by us, please contact us immediately. Privacy - Please be aware that information provided in response to this email may contain personal information, which Classic Blue may collect, and use for the purposes of marketing information technology products and services to you. For further information regarding Classic Blue's privacy policies please refer to www.classicblue.com.au
............................................................................................................................
</pre></BODY>
</HTML>