Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!news.glorb.com!news-out.readnews.com!transit3.readnews.com!panix!gordon From: John Gordon Newsgroups: comp.lang.python Subject: Re: Why BOM in logging message? Date: Wed, 9 Jan 2013 23:19:14 +0000 (UTC) Organization: PANIX Public Access Internet and UNIX, NYC Lines: 19 Message-ID: References: NNTP-Posting-Host: panix2.panix.com X-Trace: reader1.panix.com 1357773554 29040 166.84.1.2 (9 Jan 2013 23:19:14 GMT) X-Complaints-To: abuse@panix.com NNTP-Posting-Date: Wed, 9 Jan 2013 23:19:14 +0000 (UTC) User-Agent: nn/6.7.3 Xref: csiph.com comp.lang.python:36526 In roy@panix.com (Roy Smith) writes: > What's weird is that two of the servers, and only those two, stick a > BOM (Byte Order Mark) in front of the message they log. It shows up > in syslog as: > 2013-01-09T00:00:00+00:00 web5.songza.com 2013-01-0900:00:00,754 [18979]: [etc...] I worked on an application that would insert a BOM in syslog messages if the logged message contained unicode, but not if it was plain ascii. Not sure if this relates to your issue, but it's similar enough that it seemed worth mentioning. -- John Gordon A is for Amy, who fell down the stairs gordon@panix.com B is for Basil, assaulted by bears -- Edward Gorey, "The Gashlycrumb Tinies"