Specifying maximum output file size does not work
When trying to run a job that converts raw ArgoNeuT data to ROOT format I attempted to use the RootOuput maxFileSize parameter to limit the output to be <= 1GB. The job produced a file of size 1.6 GB. Chris looked into the reason for that and found that the hook for checking the output file size and triggering the re-open was disabled unintentionally during the conversion from fw.
It would be helpful to have this facility in place in the future releases. If it is easy to fix, v0.5.3 would be nice, but the release after is also acceptable.