Skip to content

Daemonizing workspace-control creates duplicate log entries #103

Closed
priteau opened this Issue Jul 3, 2012 · 0 comments

1 participant

@priteau
Nimbus member
priteau commented Jul 3, 2012

After workspace-control has been daemonized (for example during propagate and unpropagate), it logs each entry twice:

2012-07-03 13:29:35,610 - wc_daemonize:22 - WARNING - Daemonizing, goodbye.
2012-07-03 13:29:35,725 - Common:254 - DEBUG - file logging enabled, path = '/opt/nimbus/var/workspace-control/logs//wclog-2012-07-03--wrksp-1-propagate--13.29.35'
2012-07-03 13:29:35,725 - Common:254 - DEBUG - file logging enabled, path = '/opt/nimbus/var/workspace-control/logs//wclog-2012-07-03--wrksp-1-propagate--13.29.35'
2012-07-03 13:29:35,725 - Common:256 - DEBUG - trace enabled for fileloglevel
2012-07-03 13:29:35,725 - Common:256 - DEBUG - trace enabled for fileloglevel
@priteau priteau was assigned Jul 3, 2012
@priteau priteau added a commit that closed this issue Jul 3, 2012
@priteau priteau Don't write duplicate log entries after being daemonized
After being daemonized for the propagate and unpropagate operations,
workspace-control would write duplicate log entries. This happens
because we don't remove the old log handler before adding a new one.
We now remove the log handler when we are closing the log file before
forking.

Closes #103.
73173b5
@priteau priteau closed this in 73173b5 Jul 3, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.