cfml

Q: what will Lucee do if for some reason a `writeLog` call cannot write to the logfile concerned? Let's say the file has been changed to read-only, or is locked-open by some other process or similar.

They show up in the error stream.  In some cases, that is just written to the screen, in some cases it will be in catalania.out (for Tomcat), and sometimes, your container engine outputs it elsewhere...

I don't think the actual log content shows up in the error stream, BUT you will see that it couldn't write to the file.

Is that a long-winded way of saying "an exception is thrown"? IE: the `writeLog` call errors-out

I am seeing logging *stopping* (this has been raised before), but no outward indication of anything going wrong: eg, the `writeLog` line erroring out, thus surfacing the problem.

I have not investigated much yet, but it seemed to me like Lucee could be silently failing and swallowing the error situation. I say this because the logging _seemed_ to stop as soon as I started to tail the file. I don't think tailing a file ought to cause a problem (because, like, it's what `tail` _does_), but who knows. Could be a very odd coincidence.

Lucee does also have past for for trying to remediate error situations itself instead of just going "yeah that didn't work" and erroring out, like one might expect it to.

BTW was on the wrong track with this. It's not stopping writing to the log, it's resetting the log level to ERROR, so the INFO records stop getting logged :confused: