I committed to the repository a solution to the issue of logging to a
specific virtual host log file during interpreter initialization
(ChildInitScript). Scott, would you kindly check if it works for you?
Thank you
-- Massimo
On 11/05/23 09:15, Scott Pitcher wrote:
Ah thanks. Yes I've got 4 vi
Good. We can do much better on this issue. I'm going to take on the task
of analyzing a possible solution. It should be feasible and it's a
further reason for releasing 3.2.3
-- Massimo
On 11/05/23 09:15, Scott Pitcher wrote:
Ah thanks. Yes I've got 4 virtual hosts and now I've found the log
Ah thanks. Yes I've got 4 virtual hosts and now I've found the log
messages in the main logs under /var/log/apache2/
I was having init problems and without the log messages I was shooting
in the dark. Thanks again :)
Kind regards,
Scott
On 10/5/23 23:25, Massimo Manghi wrote:
Perhaps yo
Perhaps you're running the script for a virtual host with an ErrorLog
different from the default virtual host log file.
Virtual hosts get their own server record structure and
::rivet::apache_log_error can tell which virtual host is serving a
request from the server_rec structure pointed from
Hi Scott,
It does work for us.
In our Init script we use this proc, and we call it when log is needed.
The logs appear in the apache log file.
#
-
# Global loggin
#
Hi,
I have a website with a RivetServerConf ChildInitScript pointing to a
tcl script. The script works and operates normally. The only command
that does not work is /::rivet::apache_log_error/. The following command
in the script produces no log message:
::rivet::apache_log_error alert "chil
