ecore: lower priority of some intrusive logs.

Summary:
After fixed logging to journald there is lots of prints like
Jan 15 16:04:21 localhost system_server[1017]: enter idling=1 fds=1 events=0 timers=0 (next=17.14) idlers=0

Jan 15 16:04:21 localhost system_server[1017]: leave, timeout = 0

Change-Id: Id26e37a55ddaad36094308ac7fd09767cf659c04
Signed-off-by: Vasyl Vavrychuk <vasyl.vavrychuk@globallogic.com>

Reviewers: cedric

Reviewed By: cedric

Subscribers: cedric

Differential Revision: https://phab.enlightenment.org/D1875

Signed-off-by: Cedric BAIL <cedric@osg.samsung.com>
This commit is contained in:
Vasyl Vavrychuk 2015-01-20 19:13:29 +01:00 committed by Cedric BAIL
parent c25ba993f6
commit 62dd6d6dd4
1 changed files with 2 additions and 2 deletions

View File

@ -624,7 +624,7 @@ _ecore_main_gsource_prepare(GSource *source EINA_UNUSED,
ready = TRUE;
in_main_loop--;
INF("leave, timeout = %d", *next_time);
DBG("leave, timeout = %d", *next_time);
_ecore_unlock();
/* ready if we're not running (about to quit) */
@ -700,7 +700,7 @@ _ecore_main_gsource_dispatch(GSource *source EINA_UNUSED,
idlers_ready = _ecore_idler_exist();
in_main_loop++;
INF("enter idling=%d fds=%d events=%d timers=%d (next=%.2f) idlers=%d",
DBG("enter idling=%d fds=%d events=%d timers=%d (next=%.2f) idlers=%d",
ecore_idling, ecore_fds_ready, events_ready,
timers_ready, next_time, idlers_ready);