On Thursday, March 18, 2004 1:57 AM
Steven Shults <[EMAIL PROTECTED]> wrote:
> below is the output of bin/PostMasterPOP3.pl -d2 followed by the logs
> from
> the AdminLog page. there are no logs at /var/log/otrs.log where i
> told
> installer.pl to write the logs to.
I guess you told him to write the logs to var/log/otrs.log? or Syslog?
Anyway, look it up in Config.pm:
$Self->{LogModule} = 'Kernel::System::Log::File';
$Self->{'LogModule::LogFile'} =
'<OTRS_CONFIG_Home>/var/log/otrs.log';
For sure you may choose whatever location you want, /var/log is fully
ok.
> to me it looks like otrs isn't even seeing the changes in Config.pm
> Is
> there anything i need to do after editing Config.pm for the changes to
> take effect? I've tried 'rcotrs restart' to no avail.
It depends. Safest is 'rcotrs restart-force', but a 'rcotrs restart'
should get you wehre you want to.
You may well test if Config.pm's changes are recognized at a glance.
Open a Ticket, zoom on it, then toggle $Self->{TicketZoomExpand} in
Config.pm and save it. Refresh your browser.
What version of PostMaster.pm are you using?
Fr�hlich gr��t
Robert Kehl
--
There are 10 types of people in the world:
Those who understand binary, and those who don't.
_______________________________________________
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/
