Opened 9 years ago

Closed 9 years ago

#1108 closed defect (fixed)

rasnet prints too much output in nohup.out

Reported by: Dimitar Misev Owned by: Vlad Zamfir
Priority: major Milestone: 9.2
Component: rasnet Version: development
Keywords: Cc: Alex Toader
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 by Alex Toader, 9 years ago

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 by Dimitar Misev, 9 years ago

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

comment:3 by Alex Toader, 9 years ago

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 by Dimitar Misev, 9 years ago

This is already the case:

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


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

comment:5 by Alex Toader, 9 years ago

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 by Alex Toader, 9 years ago

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.