func logrotate fix

[Mike McGrath]

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?

	-Mike

[Dennis Gilmore]

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 +1's? 
+1 

reducing un-needed spam is good

Dennis

[Jeroen van Meeuwen]

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

[Ricky Zhou]

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

[Xavier Lamien]

On Mon, Sep 29, 2008 at 12:29 AM, Mike McGrath <mmcgrath(a)redhat.com&gt; 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

-- 
Xavier.t Lamien
--
http://fedoraproject.org/wiki/XavierLamien
GPG-Key ID: F3903DEB
Fingerprint: 0F2A 7A17 0F1B 82EE FCBF 1F51 76B7 A28D F390 3DEB

[Jon Stanley]

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.

On 9/28/08, Xavier Lamien <laxathom(a)fedoraproject.org&gt; wrote:
>  On Mon, Sep 29, 2008 at 12:29 AM, Mike McGrath
> <mmcgrath(a)redhat.com&gt; 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
>
>  --
>  Xavier.t Lamien
>  --
>  http://fedoraproject.org/wiki/XavierLamien
>  GPG-Key ID: F3903DEB
>  Fingerprint: 0F2A 7A17 0F1B 82EE FCBF 1F51 76B7 A28D F390 3DEB
>
>  _______________________________________________
>  Fedora-infrastructure-list mailing list
>  Fedora-infrastructure-list(a)redhat.com
>  https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
>  
-- 
Sent from my mobile device

Jon Stanley
Fedora Bug Wrangler
jstanley(a)fedoraproject.org

[Mike McGrath]

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 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.
>  
Next time you get laughed at tell those laughing that they should work to
design a more flexable environment where risks are properly evaulated
instead of blindly feared.  Having control over your environment is
important, when your environment has control over you, you've done it
wrong :)

	-Mike


>  On 9/28/08, Xavier Lamien <laxathom(a)fedoraproject.org&gt; wrote:
>  > On Mon, Sep 29, 2008 at 12:29 AM, Mike McGrath <mmcgrath(a)redhat.com&gt; 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
>  >
>  > --
>  > Xavier.t Lamien
>  > --
>  > http://fedoraproject.org/wiki/XavierLamien
>  > GPG-Key ID: F3903DEB
>  > Fingerprint: 0F2A 7A17 0F1B 82EE FCBF 1F51 76B7 A28D F390 3DEB
>  >
>  > _______________________________________________
>  > Fedora-infrastructure-list mailing list
>  > Fedora-infrastructure-list(a)redhat.com
>  > https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
>  >
>
>  --
>  Sent from my mobile device
>
>  Jon Stanley
>  Fedora Bug Wrangler
>  jstanley(a)fedoraproject.org
>
>  _______________________________________________
>  Fedora-infrastructure-list mailing list
>  Fedora-infrastructure-list(a)redhat.com
>  https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
>

[Jeroen van Meeuwen]

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 change freeze I'd be laughed out of the room and told to wait.
>   
When such a thing happens, and it does, I wait for the big outage I 
can't recover from without changing stuff during a change freeze, and 
drag their sorry asses back in the conference room.

First thing on the agenda of course is appending "> /dev/null" to the 
condrestart of some logrotate file, not the outage.

-Jeroen

[Yaakov Nemoy]

On Sun, Sep 28, 2008 at 7:28 PM, Jon Stanley <jonstanley(a)gmail.com&gt; 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.

-Yaakov
>  On 9/28/08, Xavier Lamien <laxathom(a)fedoraproject.org&gt; wrote:
> > On Mon, Sep 29, 2008 at 12:29 AM, Mike McGrath <mmcgrath(a)redhat.com&gt; 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