[tor-bugs] #9494 [Tor]: Log fix facility and lines

[Tor Bug Tracker & Wiki]

#9494: Log fix facility and lines
----------------------+-----------------------------------------------------
 Reporter:  grarpamp  |          Owner:                    
     Type:  defect    |         Status:  new               
 Priority:  normal    |      Milestone:  Tor: 0.2.4.x-final
Component:  Tor       |        Version:  Tor: 0.2.3.25     
 Keywords:            |         Parent:                    
   Points:            |   Actualpoints:                    
----------------------+-----------------------------------------------------

Comment(by grarpamp):

 In the syslog world we call it 'facility.level'. Tor calls it
 '[domain]severity'.
 Yes, I dumped it with usr1.

 Each new line (termed with '\n', or the close of the call I think) should
 be
 prefixed with time, level and domain, if configured to show that, which
 they were...
   log debug stdout
   logmessagedomains 1
 but they didn't... in part, in two separate cases.


 Also, I just tried sending debug to syslog and got...

   Aug 16 00:00:00 <daemon.notice> host Tor[pid]: message

 While the Tor's 'severity' might match up linearly with the levels of say
 FreeBSD's syslog below (I didn't check Tor's name number map /
 ordering)...
      emerg, alert, crit, err, warning, notice, info, debug
 the 'domains' do not match facilities of course. So in addition to
 the prefixing issue above, I think when syslog is destination,
 'logmessagedomains 1' should print themselves in syslog too.
 Might as well add a 'syslogfacility (default: daemon)' option
 too so folks can send it to localN, etc.
 I'm pretty sure 'warn/WARN' is deprecated for 'warning/WARNING',
 posix may say about that, might be OS dependant too.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9494#comment:2>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online