> On Dec 8, 2016, at 4:07 PM, Reindl Harald <[email protected]> wrote: > > > > Am 09.12.2016 um 01:03 schrieb Shu Kit Chan: >> Recently we moved logging and metrics configuration files from XML >> format to lua. Thus making luajit a requirement for these changes. >> >> https://docs.trafficserver.apache.org/en/latest/admin-guide/files/logging.config.en.html >> https://docs.trafficserver.apache.org/en/latest/admin-guide/files/metrics.config.en.html > > oh - those both where ATS 7.0 is too stuoid to start if they don't exist and > /etc is read-only > > FATAL: [RollBack::Rollback] Unable to find configuration file metrics.config. > Creation of a placeholder failed : Permission denied
Yes, we really should remove the rollbacks. I think this is a holdover from the days when Traffic Server was a cache appliance. There’s no UI or reasonable way to use rollbacks these days. > it's ridiculous to rely on configs which obviously could be created at start > from scratch as well as write configs in scripting languages Well, I beg to differ on this. I’ve found it quite helpful to be able to parse JSON in logging.config. I don’t expect many people will extend metrics.config, but it was well worth it to remote the XML. In general, we want to make Traffic Server more programmable, so the embedded Lua will not be going away. > - especially when those scripting languages are part of the bundeled source > instead using system libraries We used to have autoconf checks to build against the system Lua, but removed it in favor of the bundled LuaJIT install. LuaJIT is actually required since on Linux x86_64 it calls C++ destructors across Lua error handlers. I’d be happy to take a patch to optionally build against the system’s LuaJIT. J
