If its entered as /tmp/otrs.log then its going to the root, not relative to
where its called from.. If you wanted that relative then you want
tmp/otrs.log. Mine is set to /opt/otrs/tmp/otrs.log but would also work if I
did tmp/otrs.log (because /opt/otrs is my home directory and considered the
root of the application)
In other words if you put '/' at the beginning its like going to the root of
the drive.
HTH,
Andy
On 7/11/06 3:12 PM, "s taylor"
Thanks for your reply.
I have 'write' permissions on the folder; enough that the file, 'Kernel-System-Stats-StateAction-2006-06.cache' was able to write to it a few days ago.
For the SysLog file in SysConfig, I have '/tmp/otrs.log' as the LogFile name (using the default) which I'm ASSUMING that this implies that this folder is located in the 'var' subdirectory.
As another attempt, I manually created the 'otrs.log' file with 777 and placed it in '/tmp/otrs.log' (which is contained in 'var') subdir. I logged in then out of a test account in order to generate a line entry in the log. The 'System Log' on the web interface was updated, but nothing was written to the 'otrs.log' file I created.
Any ideas?
Thanks.
_______________________________________________ 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 orr consulting for your OTRS system? => http://www.otrs.com/
--