Have a dive into your Kernel/Config.pm, there you'll find your logging
mechanism, either:
$Self->{LogModule} = 'Kernel::System::Log::SysLog';
or:
$Self->{LogModule} = 'Kernel::System::Log::File';
$Self->{'LogModule::LogFile'} = '/tmp/otrs.log';
The last line may state another directory - the above is from
Default.pm. Actually, /tmp gets cleared on many systems during (or prior
to) a reboot, so I'd advice to use /var/log/otrs.log or similar instead.
For sure, syslog is the recommended logging mechanism as all your syslog
tools are available then.
Note: On Windows, you cannot use the syslog option, as Windows doesn't
come with a syslog facility, so you'll probably find the latter version
then. If you managed to run syslog on Windows, please tell me ;) I
didn't so far, although there are syslog server components out there.
Later. Doesn't matter now.
Your Apache logs are here:
Linux:
/var/log/http/ or
/usr/apache/logs or
/var/log/apache or
similar. httpd.conf tells more.
Windows:
<apache-inst-dir>\logs\
hth,
Robert Kehl
----- Original Message -----
From: "Wes Plate"
On 9/18/03 8:23 AM, "Robert Kehl" wrote:
Nromally, the (un)lock timeouts (that's what you really mean?) are meant to be fully functional. Could you provide something from your logs?
Sure thing!
Where do I find the logs you're interested in?
-- Wes Plate Automatic Duck, Inc. http://www.wesplate.com http://www.automaticduck.com
_______________________________________________ OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs Support oder Consulting für Ihr OTRS System? => http://www.otrs.de/