Just wondering if anyone has already developed an optimised log buffer script, i.e. that accepts strings via LINK messages as input, buffers these up in a string until a threshold is hit (key is trying to maxmise this level), and then sends whole string out via email and clears the buffer.
Has anyone got an optimised script that deals with the issues such as:
* if I send the large string out to my normal email handling scripts they buffer overflow (memory issue) due to the large string
* if I send the email out within the log buffer script I'll hit the email delay for that script - not sure how many log messages could build up in the LINK message buffer and whether this may be ok or not (i..e not wanting to lose incoming log messages) - also whilst events are building up in the LSL buffers (before being processed by the script) I assume they don't take up script memory?
* perhaps best approach is to have one cutdown email sending script that is specifically designed to work with only the log buffer script, and is tested to be able to handle the max size of the string buffer
So far with the normaly overheads I usually put into my script (e.g. for admin commands etc) I've only been able to get the string length threshold up to around 2200 characters.
Cheers