Page MenuHomePhabricator

output written to the console during a dump run should go to a local log file as well
Closed, ResolvedPublic


A bunch of output gets reported, including startup of processes, number of revisions processed at any given time, errors encountered when retrieving revisions, etc. Right now these all go into the ether since the whole thing runs in a screen session. They should get written into a log file so that we can see when something dies instead of having any relevant messages long since scrolled off the virtual screen.

Version: unspecified
Severity: minor



Event Timeline

bzimport raised the priority of this task from to Medium.Nov 21 2014, 11:12 PM
bzimport set Reference to bz27148.

fixed in my branch and deployed; specified by command line option to Not included (but probably ok): debugging output from