ensuring that the service is disabled and not running is enough for me...
Be sure to make a dependency between them to reduce the time you are
running without a log
Ohad

On 9/24/08, Larry Ludwig <[EMAIL PROTECTED]> wrote:
>
> Sorry I gave you the wrong bit.  That was for a badly installed older
> version of syslog-ng
>
>         # remove old sysklogd (hack) only if exists. Does not follow
> standard upgrade
>         exec { "remove-sysklogd":
>                 name      => "rpm -e --nodeps --allmatches sysklogd",
>                 logoutput => true,
>                 onlyif    => "rpm -q sysklogd",
>         }
>
> On Sep 24, 10:46 am, Larry Ludwig <[EMAIL PROTECTED]> wrote:
>> If you are using RHEL or CentOS you should also remove sysklogd.
>>
>> I do it this way:
>>
>>         # remove old syslog-ng (hack) only if exists. Does not follow
>> standard upgrade
>>         exec { "remove-syslog-ng-1.6.2-2":
>>                 name      => "rpm -e --nodeps --allmatches syslog-
>> ng-1.6.2-2",
>>                 logoutput => true,
>>                 onlyif    => "rpm -q syslog-ng-1.6.2-2",
>>         }
>>
>> Talk to me offline tonight at the Puppet get together.
>>
>> -L
>>
>> --
>> Larry Ludwig
>> Empowering Media
>> 1-866-792-0489 x600
>> Fully Managed VPSeshttp://www.hostcube.com/
>>
>> On Sep 22, 3:30 pm, "Brian Gupta" <[EMAIL PROTECTED]> wrote:
>>
>> > Anyone have any recipes for this? Also logrotate bits would help.
>>
>> > --
>> > - Brian Gupta
> >
>

-- 
Sent from Gmail for mobile | mobile.google.com

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to