On Sun, Sep 28, 2008 at 7:28 PM, Jon Stanley [EMAIL PROTECTED] 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
On Sunday 28 September 2008 05:29:14 pm Mike McGrath 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
to
/etc/init.d/funcd condrestart /dev/null
Can I get 2
Mike McGrath 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
to
/etc/init.d/funcd condrestart /dev/null
Can I get 2 +1's?
Sounds reasonable to me, +1.
-Jeroen
On 2008-09-28 05:29:14 PM, Mike McGrath 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
to
/etc/init.d/funcd condrestart /dev/null
Can I get 2 +1's?
+1
On Mon, Sep 29, 2008 at 12:29 AM, Mike McGrath [EMAIL PROTECTED] 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
to
/etc/init.d/funcd condrestart /dev/null
Can
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
On Sun, 28 Sep 2008, Jon Stanley 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
Jon Stanley 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
