Reply To: Trouble with automated cycling of SMAT files

[Mike Grieger]

Yes!  I have seen this before as well.  I have seen it happen where thread names are named similarly.  hcicyclesavemsgs is a perl script that primarily uses another perl script – hciconnstatus – to operate.  Default return by hciconnstatus only has 15 characters for a thread name, so if 2 threads have name patterns the same through 15 characters, you could have the first thread that matches cycle multiple times.  (If you happen to dump to output of the hcicyclesave off to a log, it should show you what is cycling/attempting to cycle and you would see this.)

Anyway, we’ve modified our hciconnstatus (bin directory) so that our thread names display and use 28 characters, as we try to use descriptive thread names that typically are more than 15 characters long.

< hciconnstatus snippet >

#    FACTORY SETTINGS ARE BELOW, COMMENTED OUT per Mike G

#    set hfmt “%-15.15s %-15.15s %-10.10s %-15.15s %-20.20s” ;# Heading format

#    set fmt “%-15.15s %-15.15s %-10.10s %-15.15s %-20.20s” ;# Output line format

#    echo [format $hfmt Process Connection State “Proto Status” When]

#    echo ”

---

---

---

---

---

“

   set hfmt “%-15.15s %-28.28s %-5.5s %-7.7s %-20.20s” ;# Heading format

   set fmt “%-15.15s %-28.28s %-5.5s %-7.7s %-20.20s” ;# Output line format