<!DOCTYPE html><html><head><title></title><style type="text/css">p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div>On our weekly call this morning, we were talking about moving toward standardizing the format of Cyrus logs. My interest here is in making it easy for a program to read and classify logs. That's not as simple as it could be, right now, because often a log line is sprintf-'d with parameters. Even worse, sometimes those parameters have spaces in them.<br></div><div><br></div><div>I think we all agree on something like this:<br></div><ul><li>produce a macro that does the logging in a standard format<br></li><li>the format leads with a "category", which is a fixed string<br></li><li>extra data to be included show up like auditlog does it: foo=<x> bar=<y><br></li><li>by using a macro, we can get the location (file, function) from which the log line is being emitted<br></li></ul><div><br></div><div>Next steps:</div><ul><li>agree on the specifics of the above and that it's the way to log in new code<br></li><li>start converting old code (prioritized by value of reading lines from each part of the code)<br></li></ul><div><br></div><div>Further thoughts before we get on to specifics?</div><div><br></div><div id="sig65535536"><div>-- <br></div><div>Ricardo Signes (rjbs)<br></div></div></body></html>