Hello Charles Marcus Am 2014-07-08 20:08, schrieb Charles Marcus: > > There is one specific type of error that shows up formatted differently... > > Virtually all of the log lines start with Mmm DD TT:TT:TT, like this: > > Jul 08 13:09:10 sogod [32691]: [ERROR] > <0x0x7ff375ee3c50[NGLdapAttribute]> could not convert value of > objectGUID to string > > except for these, which start with YYYY-MM-DD TT:TT:TT: > > 2014-07-08 13:09:26.547 sogod[32622] > ERROR(-[NGLdapSearchResultEnumerator nextObject]): does not support > result references yet > .. >
Sorry, don't know why that one is different. > Also, after the seconds, there is a period followed by a 3 digit > number... what is that? Ie, in the above, 13:09:26.547 - what is that .547? > That is the second fraction. You get these timestamps with a higher precision, down to milliseconds. > These lines formatted differently only show up very rarely, but when > they do, those last digits are always in increments, sometimes > sequential, but if not, only one or two numbers are skipped... > > Ie, these: > > 2014-07-08 11:03:56.205 sogod[31654] > 2014-07-08 11:03:56.206 sogod[31654] > 2014-07-08 11:03:56.208 sogod[31654] > 2014-07-08 11:03:56.209 sogod[31654] > So this is only a fast logging in milliseconds. Kind regards, Christian Mack -- Christian Mack Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung Basisdienste 78457 Konstanz +49 7531 88-4416
smime.p7s
Description: S/MIME Cryptographic Signature
