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
#
-----------------------------------------------------------------------------
proc log {sev txt} {
if {[string equal $sev ERROR]} {
::rivet::apache_log_error err $txt
} else {
::rivet::apache_log_error notice $txt
}
}
On Wed, May 10, 2023 at 8:14 AM Scott Pitcher <
sco...@svptechnicalservices.com.au> wrote:
> 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 "childinit.tcl running ..."
>
> The code execute and I I change the level from alert to some random string
> like abcdef for example, then the script doesn't run at all and when the
> normal session script runs, the child hasn't opened the databases and the
> client script fails too.
>
> Is there a way of logging from the ChildInitScript?
>
> Kind regards,
> Scott
>
>
> --
> +--------------------------------------------------------------------------------+
> | ... will make the wilderness a pool of water, the dry land springs of water
> ...|
> +--------------------------------------------------------------------------------+
> | Scott Pitcher
> sco...@svptechnicalservices.com.au |
> | +61-3-9008-5695 (B) +61-479-042-834
> (M) |
> | SVP Technical Services ABN 79 220 496
> 603 |
> |PGP: https://gnupg.org/
> |
> |KEY: https://pgp.mit.edu/pks/lookup?op=vindex&search=0xEDBE43639EFD884D
> |
> +--------------------------------------------------------------------------------+
>
> DISCLAIMER:
> The content of this email is confidential and strictly intended only for the
> recipient(s) specified in the message. If you have received this message by
> mistake it is strictly forbidden to keep this email in any form, electronic or
> hard copy, or to share any part of it with any one else, without the prior,
> written consent of the author. If you have received this message by mistake,
> please let me know by replying to this email, and then destroy it and any
> copies.
>
> SECURITY:
> I prefer to send and receive confidential messages protected by PGP public key
> encryption. If you are willing to or are interested in protecting our email
> communication with PGP encryption, please refer to https://gnupg.org/.
>
>
