On Thu, 9 May 2013 13:58:45 -0700 (PDT)
John Simpson wrote:
> I've done the following, it ended up being a bit simpler for me when
> I'm not sure what random services a new CentOS install has installed
> and/or enabled...
>
> define no_service ( ) {
> service { "${name}" :
> ensure =
I've done the following, it ended up being a bit simpler for me when I'm
not sure what random services a new CentOS install has installed and/or
enabled...
define no_service ( ) {
service { "${name}" :
ensure => stopped ,
enable => false ,
status => "stat -t /etc/rc?.d/S?
On Tue, Jan 17, 2012 at 1:09 PM, Christopher Wood
wrote:
> I definitely need some assistance in conceptualizing something.
>
> If I want to configure syslog-ng instead of rsyslog, or configure rsyslog
> instead of sysklogd, the previous syslog daemon has to be stopped (and
> disabled) before the
On Tue, Jan 17, 2012 at 13:09, Christopher Wood
wrote:
> I definitely need some assistance in conceptualizing something.
>
> If I want to configure syslog-ng instead of rsyslog, or configure rsyslog
> instead of sysklogd, the previous syslog daemon has to be stopped (and
> disabled) before the
I definitely need some assistance in conceptualizing something.
If I want to configure syslog-ng instead of rsyslog, or configure rsyslog
instead of sysklogd, the previous syslog daemon has to be stopped (and
disabled) before the new one starts. De-configuring the previous one works just
fine w
