-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2023-03-11 at 13:10 +0100, Per Jessen wrote:
Per Jessen wrote:
This week I've been working on a small proxy daemon for nginx, hopefully it will reduce the memory footprint on mailman3. It writes some warnings -
message( 0, "Unable to allocate %luMb for map", message( 0, "something went wrong, %s could not be loaded", mapfile ); message( 0, "map loaded, %u invalid entries", inv ); message( 0, "getaddrinfo(%s) failed: error %d: %s\n", hostname, rc, gai_strerror(rc) ); message( 0, "socket() failed: error %d: %s\n", errno, strerror(errno) ); message( 0, "bind() failed: error %d: %s\n", errno, strerror(errno) ); message( 0, "listen() failed: error %d: %s\n", errno, strerror(errno) ); message( 0, "select() failed: error %d; %s", errno, strerror(errno) );
So Carlos, with your built-in sense for what is debug, warning and error - how would you deal with the above?
Anything worth reporting to the developer?
They don't seem to me entries from the /var/log/warn file, and I'm not familiar with that tool. They seem to me cryptic debug messages intended to be understood only by the programmer, so they should not be written to "/var/log/warn" file. If I find those things in MY "/var/log/warn" file, I might write a bugzilla so that they are sent elsewhere. And/Or, I might write a filter to rsyslog to delete them from "/var/log/warn". I have many already. - -- Cheers, Carlos E. R. (from openSUSE 15.4 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCZBYm4xwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfV2AAAoIt17gh5MxO7l5ucgu+U no3p3VOrAJwOoUyBVeyr8tMPXqCV4Vpl3hhYXQ== =nvvm -----END PGP SIGNATURE-----