On Thu, Jan 7, 2021, at 1:27 PM, costavitor...@gmail.com wrote:
> Hi
>
> Is it possible to log to console?
>
> I've changed gunicorn configuration:
> accesslog='-'
> errorlog='-'
Which file did you change to apply these configurations?
>
> Then logs are not written to log files, but I can't see what's being logged.
>
> I'm on a docker environment and having log files it's something that I
> want to avoid to control disk usage.
> And I'm capturing what's shown in console, so it was great if I could
> log into console.
There are a couple of loggers the Mailman Core uses and you can set their
logging path to be `/dev/stdout` to log to standard output which I think your
container manager should be able to grab. Unfortunately, there isn't a way yet
to change all of their "path" using a single config, so you'd have to do it
individually for each of them.
The available loggers are:
# - archiver-- All archiver output
# - bounce -- All bounce processing logs go here
# - config -- Configuration issues
# - database-- Database logging (SQLAlchemy and Alembic)
# - debug -- Only used for development
# - error -- All exceptions go to this log
# - fromusenet -- Information related to the Usenet to Mailman gateway
# - http-- Internal wsgi-based web interface
# - locks -- Lock state changes
# - mischief-- Various types of hostile activity
# - plugins -- Plugin logs
# - runner -- Runner process start/stops
# - smtp-- SMTP activity
# - subscribe -- Information about leaves/joins
# - vette -- Message vetting information
And you can set their logging path by adding the following (for example) to
your mailman.cfg
[logging.archiver]
path: /dev/stdout
Same goes for the rest of the loggers.
Hope this is helpful!
--
thanks,
Abhilash Raj (maxking)
___
Mailman-Developers mailing list -- mailman-developers@python.org
To unsubscribe send an email to mailman-developers-le...@python.org
https://mail.python.org/mailman3/lists/mailman-developers.python.org/
Mailman FAQ: https://wiki.list.org/x/AgA3
Security Policy: https://wiki.list.org/x/QIA9
