Clovertech

hcimonitord log configuration

› Clovertech Forums › Read Only Archives › Cloverleaf › Cloverleaf › hcimonitord log configuration

  • Creator
    Topic
  • May 7, 2013 at 3:42 pm #53644
    Yves Guerin
    Participant

      Dear,

      I discover that the hcimonitord logs error messages in hcimonitord.err and hcimonitord.log:

      Code:

      [aler:aler:ERR /0:_hcimonitord_:04/23/2013 11:25:39] No valid LASTS available for bdmMCH_out, skipping alert #12


      Same line !!??  So the hcimonitord.log is very big, too big.

      creation time:

      Code:

      [prod:prod:INFO/0:_hcimonitord_:05/01/2013 00:01:04] Informing clients of monitord log cycle end


      size after 7 days: 49035163 kb

      If I understand, cloverleaf uses the same technic as syslogd: FACILITY/PRIORITY = aler:aler:ERR

      So How to configure hcimonitord to get PRIORITY “ERR” to be send to the error log not the log itself ?

      We already rotate the log file via crontab every month.

      Regards,

      Yves

    • Creator
      Topic
    • The forum ‘Cloverleaf’ is closed to new topics and replies.