logging config parameter is ignored

Bug #277953 reported by Jehiah
4
Affects Status Importance Assigned to Milestone
txLoadBalancer
New
Low
Duncan McGreggor

Bug Description

now that this is ported to twisted, the logging config parameter seems to be ignored

when starting up with 'twistd -noy /path/to/txlb.tac' logging is output to stdout (or stderr?) regardless of the logging xml directive. When dropping the -n parameter so twistd demonizes logging goes to ./twistd.log in the current working directory, also regardless of the logging directive

when not specified in the config file logging should be to stdout, when specified it should be to a file, and there should also perhaps be a way to disable logging? (or i suppose we could use /dev/null on a linux box)

Related ticket:
  https://bugs.launchpad.net/txloadbalancer/+bug/280577

Jehiah (jehiah)
description: updated
Changed in txloadbalancer:
assignee: nobody → oubiwann
importance: Undecided → Medium
status: New → Won't Fix
Revision history for this message
Duncan McGreggor (oubiwann) wrote :

Hrm. Don't know why this was set as "Won't Fix" -- it will be :-)

Changed in txloadbalancer:
status: Won't Fix → New
description: updated
Revision history for this message
Duncan McGreggor (oubiwann) wrote :

Hrm. Actally, I'm not sure about this bug now.

I've changed all the internal logging to Twisted's logging mechanism and removed the old, custom logging module that was written for PythonDirector.

In Twisted applications, logging is controlled via application startup... so maybe the configuration option can be used at the application level (.tac file or from the command line with twistd). Dunno yet. I'll have to give this some more thought.

Changed in txloadbalancer:
importance: Medium → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.