Anonymous | Login | Signup for a new account | 12-17-2024 14:49 PST |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Advanced Details [ Jump to Notes ] | [ View Simple ] [ Issue History ] [ Print ] | ||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
0000820 | [Resin] | minor | always | 01-06-06 09:48 | 01-19-06 14:34 | ||||
Reporter | ferg | View Status | public | ||||||
Assigned To | ferg | ||||||||
Priority | urgent | Resolution | fixed | Platform | |||||
Status | closed | OS | |||||||
Projection | none | OS Version | |||||||
ETA | none | Fixed in Version | 3.0.18 | Product Version | 3.0.17 | ||||
Product Build | |||||||||
Summary | 0000820: add auto-flush to access-log | ||||||||
Description |
(rep by Rick Ross) It would be REALLY HELPFUL if you would add an option to the resin.conf to allow us to flush the logs after each line is added. When we're trying to "tail" logs to see what is causing a problem (or, more often "who" is causing a problem) we have to deal with intermittent blasts of large numbers of log lines. It would be much more valuable to be seeing a near realtime stream of log records passing by. Resin's log caching results in hundreds of lines per burst at intermittent intervals. It is much more difficult to comprehend. We don't care at all about the hit to performance. Viewing a log stream of this type is often our most effective tool for finding a problem, or a problem user. |
||||||||
Steps To Reproduce | |||||||||
Additional Information | |||||||||
Attached Files | |||||||||
|
Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
28 total queries executed. 25 unique queries executed. |