#1108 closed defect (fixed)

rasnet prints too much output in nohup.out

Reported by: dmisev Owned by: vzamfir
Priority: major Milestone: 9.2
Component: rasnet Version: development
Keywords: Cc: atoader
Complexity: Medium

Description

The logs in nohup.out should be checked, it looks like there's way too much information, somehow with DEBUG level (even though I haven't specified --enable-debug).

Change History (6)

comment:1 Changed 22 months ago by atoader

That is probably because --enable-debug is ignored. This could be easily solved by creating a different easylogging configuration file when --enable-debug is set.

comment:2 Changed 22 months ago by dmisev

I was saying the opposite, there is DEBUG level output in nohup.out which should not be there.

comment:3 Changed 22 months ago by atoader

I meant that Vlad should modify the easylogging configuration files so that debug is turned off by default. Debug should only be turned on when --enable-debug is set.

comment:4 Changed 22 months ago by dmisev

This is already the case:

* DEBUG:
    FORMAT                  =   "[%level] - %datetime, %loc: %log"
    ENABLED        	    =   false


* TRACE:
    FORMAT                  =   "[%level] - %datetime, %loc: %log"
    ENABLED        	    =   false

comment:5 Changed 22 months ago by atoader

Ok, from what I see, the code in main.cc in rasmgr_x does not initialize the logger using the class implemented by Vlad. So it's not using that file.

comment:6 Changed 21 months ago by atoader

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.