I enabled LogHistory on one of my sites to test this out. Here is what I am seeing. After enabling the LogHistory, I bounced all processes and all daemons, assuming this needed to be done in order for it to take affect. In my process directory before this, I had a .log and a .old file. When I bounced everything, it created the LogHistory directory and the most recent log file was sent to the LogHistory directory. The .old was blown away…nowhere to be found. Then I went out there from the NetMonitor and performed a “cycle output”. It did not create a .old file in the process directory but instead just moved the .log file to the LogHistory directory. If this is the case, you may want to rethink some existing scripts you have in place that deal with .old directories.
I received a reply from support. This function does not cycle the hcimonitord log only the process logs. To cycle the hcimonitord log you can run this command: hcicmd -t d -p hcimonitord [code]hcicmd -t d -p hcimonitord