Opened at 2012-09-27T19:42:01Z
Last modified at 2024-08-27T16:18:19Z
#1815 assigned defect
either bridge foolscap log messages to twistd.log, or remove the section of logging.rst about that
Reported by: | davidsarah | Owned by: | blaisep |
---|---|---|---|
Priority: | normal | Milestone: | undecided |
Component: | code | Version: | 1.9.2 |
Keywords: | logging twisted foolscap docs | Cc: | warner |
Launchpad Bug: |
Description (last modified by blaisep)
From git/docs/logging.rst@959248cd
Local twistd.log files ====================== [TODO: not yet true, requires foolscap-0.3.1 and a change to ``allmydata.node``] In addition to the foolscap-based event logs, certain high-level events will be recorded directly in human-readable text form, in the ``BASEDIR/logs/twistd.log`` file (and its rotated old versions: ``twistd.log.1``, ``twistd.log.2``, etc). This form does not contain as much information as the flogfiles available through the means described previously, but they are immediately available to the curious developer, and are retained until the twistd.log.NN files are explicitly deleted. Only events at the ``log.OPERATIONAL`` level or higher are bridged to ``twistd.log`` (i.e. not the ``log.NOISY`` debugging events). In addition, foolscap internal events (like connection negotiation messages) are not bridged to ``twistd.log``.
Change History (4)
comment:1 Changed at 2012-09-27T19:43:07Z by davidsarah
comment:2 Changed at 2024-08-27T16:16:55Z by blaisep
- Description modified (diff)
- Owner set to blaisep
- Status changed from new to assigned
comment:3 Changed at 2024-08-27T16:17:45Z by blaisep
- Status changed from assigned to new
comment:4 Changed at 2024-08-27T16:18:19Z by blaisep
- Status changed from new to assigned
Note: See
TracTickets for help on using
tickets.
I'm not sure the threshold should be >= log.OPERATIONAL though; that's possibly a bit too verbose. Maybe > log.OPERATIONAL ?