Xaphier Report post Posted April 22, 2011 The current git version has more logging and better control of what is logged. Now have have: error warning info debug debug_verbose as log levels. The log levels can be changed also per command line, using: --log_level=error|warning|info|debug|debug_verbose -ll=e|w|i|d|dv or setting the log level to debug_verbos with --debug There is also now a new FEATURE RELEASE_MODE. When used, default logging is set to info, else debug_verbose is used. Only information is logged if the log level of the information is equal of lower than the general log level. That mean, everything is logged at log level debug_verbose and only errors at log level error Share this post Link to post Share on other sites
Alberich Report post Posted April 22, 2011 Is it possible to get the old 'Last message repeated x times' back? You're writing all into an el.log now and rename old logs to el.log.x, does this go endless or is there a limit to keep only a certain number of old logs? Haven't tried the different log levels yet, will try to remember at next login. Share this post Link to post Share on other sites
hussam Report post Posted April 23, 2011 I think it rotates 10 log files. Share this post Link to post Share on other sites
Xaphier Report post Posted April 23, 2011 Yes, only 10 is the number Also, 'Last message repeated x times' is now in git, forgot it, sorry Share this post Link to post Share on other sites
Alberich Report post Posted April 23, 2011 getting some empty lines with on log level debug [14:17:57] Debug: Initializing lists [14:17:57] Debug: ... [14:18:04] Debug: Loading textures [14:18:04] Debug: ... [14:18:04] Debug: Preparing opening window [14:18:04] Debug: ... [14:18:08] Debug: Loading map [14:18:08] Debug: Loading 3D objects [14:18:08] Debug: [14:18:11]Last message repeated 35times [14:18:11] Debug: Loading 2D objects [14:18:11] Debug: [14:18:11] Debug: Loading lights [14:18:11] Debug: [14:18:11] Debug: Loading particles [14:18:11] Debug: [14:18:11] Debug: Building sectors [14:18:11] Debug: Done [14:18:11] Debug: Share this post Link to post Share on other sites
Xaphier Report post Posted April 24, 2011 Thanks, should be fixed now Share this post Link to post Share on other sites
bluap Report post Posted May 19, 2011 In the latest git, logging appears to have gone crazy. Is it deliberate to be logging so much stuff? If so, I think it's logging too much. I store my config files on a network server. My network is completely swamped for 30 seconds or so, twice during start-up, each time I resize the client window or change to a new location. Start-up time and map change times are hugely increased. Share this post Link to post Share on other sites
bluap Report post Posted May 20, 2011 (edited) After the update fix today, the volume is greatly reduced by I'm still getting the same network surges due to logging access. Looks like its enter_debug_mark() causing the problems. Edited May 25, 2011 by bluap The latest changes have restored previous performace. :) Share this post Link to post Share on other sites
Wind_of_Change Report post Posted March 16, 2012 Sorry for replying tot this topic with something only slightly relevant to this topic and somewhat cosmetic. TThe log levels can be changed also per command line, using: --log_level=error|warning|info|debug|debug_verbose -ll=e|w|i|d|dv or setting the log level to debug_verbos with --debug For consistency, could we only accept options given in this form? Right now we accept for example: -fps=1 -fps1 -fps 1 Wouldn't it be more consistent only to accept 1.? (The second option makes the command parsing harder/hackier than it should be.) Share this post Link to post Share on other sites
