Hi Rajesh, I Just closed this as submitted, but don't see the changes on the master. Do I need to reopen this one? Also can the changes to be applied back to 4.3 and 4.4?
Thanks Saurav On Tue, Apr 15, 2014 at 11:14 PM, Rajesh Battala <rajesh.batt...@citrix.com>wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/19584/#review40414 > ----------------------------------------------------------- > > Ship it! > > > Ship It! > > - Rajesh Battala > > > On April 14, 2014, 7:10 a.m., Saurav Lahiri wrote: > > > > ----------------------------------------------------------- > > This is an automatically generated e-mail. To reply, visit: > > https://reviews.apache.org/r/19584/ > > ----------------------------------------------------------- > > > > (Updated April 14, 2014, 7:10 a.m.) > > > > > > Review request for cloudstack and Jayapal Reddy. > > > > > > Repository: cloudstack-git > > > > > > Description > > ------- > > > > This will prevent the /etc/init.d/cloud script from logging messages to > /var/log/cloud/cloud.out if the CLOUD_DEBUG flag is not defined. If the > flag is defined only then will messages be logged. This is because the > cloud.out file gets rolled over once max size is reached via the log4j > settings, since the script is not aware of the log4j settings it causes the > log file to exceed its max size and fill up the file system. > > > > > > Diffs > > ----- > > > > systemvm/patches/debian/config/etc/init.d/cloud 83853bc > > > > Diff: https://reviews.apache.org/r/19584/diff/ > > > > > > Testing > > ------- > > > > The console proxy vm was started and console sessions tested. The > secondary storage vm was succesfully started. > > > > > > Thanks, > > > > Saurav Lahiri > > > > > >