This all sounds to me like there isn't much of an abstraction, since
there's no definition of what ought to happen (as opposed to what does
happen).
Surely, I want to be able to manage the xyz service in the same way no
matter what the operating system. If I take Felix' suggestion and
start hackin
On 2011-04-21 10:19, Felix Frank wrote:
> I don't think ralsh packs much intelligence in that regard, but relies
> on the redhat provider instead.
Yes, I was thinking "ralsh" as in "ralsh and all the subroutines from
the rest of Puppet that it uses".
> Peaking at the provider, it doesn't appear
On 04/21/2011 09:35 AM, Thomas Bellman wrote:
> On 2011-04-21 09:18, Felix Frank wrote:
>
>> So obviously, there is no xinetd provider. I concur that such a thing
>> would probably be worthwile. If your Ruby is good (or if you like doing
>> new things ;-), you may want to cobble one together yours
On 2011-04-21 09:18, Felix Frank wrote:
> So obviously, there is no xinetd provider. I concur that such a thing
> would probably be worthwile. If your Ruby is good (or if you like doing
> new things ;-), you may want to cobble one together yourself as a
> plugin, it's not rocket science.
Well, on
>> Also note that under the puppet paradigm, a "service" is not something
>> reachable via network (as in "services provided through xinetd"), but
>> can be any process that is maintained by use of an init-script.
>>
>> Regards,
>> Felix
>
> Hi Felix
> Any service must surely have an access point
On Wed, Apr 20, 2011 at 10:42:21AM -0700, Tim Coote wrote:
> [I'm using the training machine from puppetlabs]
> puppet resource service xinetd
Which one? Not all of them use xinetd. Certainly the CentOS 5 machine I
have doesn't have xinetd. So it won't report it as a service. Querying it
directly
Intriguingly, on a fedora 13 host, using puppet-0.25.5-1.fc13.noarch,
information about xinetd *is* returned by
puppet resource service.
the version on the learning machine is:
pe-puppet-2.6.4-7.el5
Is the change in behaviour a bug? how can I tell?
On Apr 20, 6:42 pm, Tim Coote wrote:
> Hi Ben
On 20.4.2011 20:30, Tim Coote wrote:
> On Apr 20, 8:13 am, Felix Frank
> wrote:
>> Also note that under the puppet paradigm, a "service" is not something
>> reachable via network (as in "services provided through xinetd"), but
>> can be any process that is maintained by use of an init-script.
>
On Apr 20, 8:13 am, Felix Frank
wrote:
> On 04/20/2011 03:17 AM, Ben Hughes wrote:
>
> > On Tue, Apr 19, 2011 at 04:24:18AM -0700, Tim Coote wrote:
>
> >> Is there a canonical definition of the service type abstraction, or is
> >> the definition just how the implementation behaves?
>
> > What happ
Hi Ben
[I'm using the training machine from puppetlabs]
puppet resource service xinetd
returns info about xinetd.
But
puppet resource service
does not include anything about xinetd, which sounds like a bug to me.
I understand the limitations of what can be recovered, but that's an
implementation
10 matches
Mail list logo
