On Sun, Sep 28, 2008 at 7:28 PM, Jon Stanley <jonstanley(a)gmail.com> wrote:
I'll throw a -1 in here (not that my vote matters for anything :)
Not because of any risk in the change, but rather it violates the
concept of a change freeze. It doesn't affect service, so if I went to
our change management meeting at work with something like this during
a change freeze I'd be laughed out of the room and told to wait.
In my mind, we either have change freezes and stick to them, or we
just forgo the charade.
I thought the point of a change freeze is so that we are more cautious
about changes we have to make. Since everyone seems to approve the
idea of making such a change during the change freeze, it seems
acceptable to do so.
On 9/28/08, Xavier Lamien <laxathom(a)fedoraproject.org> wrote:
> On Mon, Sep 29, 2008 at 12:29 AM, Mike McGrath <mmcgrath(a)redhat.com> wrote:
>> I'd like to implement the following global fix (its generating cron spam)
>> in /etc/logrotate.d/func_rotate I'd like to change line 8 from
>> /etc/init.d/funcd condrestart
>> /etc/init.d/funcd condrestart > /dev/null
>> Can I get 2 +1's?