Not really valid for the network/networking (debian) service - there
is no daemon, unless you count dhcpcd / networkmanager & friends.
As to the original question, I ship a modified version of the init
scripts for Ubuntu to do some $(ip link) parsing, also one-count pings
to the default gat
When I quickly realized it was using clear text I started distributing
the /var/db/shadow/hash/ file. We want no clear text.
Thanks for working on this Nigel.
On Oct 17, 2008, at 2:16 PM, Nigel Kersten wrote:
>
> Sparked off from this discussion on puppet-dev:
>
> http://groups.google.com/gr
On Fri, 2008-10-17 at 12:28 +0200, Jeroen van Meeuwen wrote:
> Kenneth Holter wrote:
> > I think I got it working by compiling from source, but I'm sure there
> > will be others that will appreciate a package RHEL 4.
> >
>
> And so I am packaging rubygem-mongrel and dependencies for EL-4, thank
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all
Puppet version 0.24.6RC2 code-named Camilla has been released and is
available for testing!
http://reductivelabs.com/downloads/puppet/puppet-0.24.6rc2.tgz
This will probably be the last RC and we'll release the full release
early next week b
Bryan Kearney wrote:
> Has anyone solved status checking for the network service on fedora?
> Since it always returns success, using 'hastatus => true' does not work.
> We have some recipes that always cause the network service to restart
> even when it does not need to.
>
Override 'pattern'.
Has anyone solved status checking for the network service on fedora?
Since it always returns success, using 'hastatus => true' does not work.
We have some recipes that always cause the network service to restart
even when it does not need to.
-- bk
--~--~-~--~~~--
Sparked off from this discussion on puppet-dev:
http://groups.google.com/group/puppet-dev/browse_thread/thread/88f60414c3dfbe5c
Who is currently using clear-text passwords with the directoryservice
provider in particular, and would you be exceedingly upset if Puppet
changed to no longer allow yo
On Oct 13, 2008, at 11:19 AM, Joel Nimety wrote:
>
>
>
> Luke Kanies wrote:
>> On Oct 13, 2008, at 10:24 AM, Joel Nimety wrote:
>>
>>
>> That would be a completely new subsystem to transactions -- instant
>> action. The 'notify' and 'subscribe' mechanisms all just involve
>> queues.
>>
>> I'm no
Marc Fournier wrote:
>>> The patch I sent indeed focused on the need for this workaround. The
>>> behaviour of Joel's patch is definitely better.
>>
>> So.. to verify... you are good?
>
> Sorry, I wasn't very clear. Yes Joel's patch works fine for me.
Great.. thank you for using it and sending a
Hi
> However it seems that I only needed to use this -p option because I made
> the pid-dir configurable, which was somehow anyway not a good idea. As
> discussed with David Lutterkort and mentioned in #1460 [1] I'll change
> the init.d scripts with the according needs and ideas and there will be
Sorry, I replied the other day, guess I forgot to hit send (always
helpful).
Anyway, So yes restarting puppet solved the problem, however, I'm
noticing 9 out of ever 10 changes require me to restart for them to
take effect. Surely this cannot be expected behavior can it?
It's working now, and re
Kenneth Holter wrote:
> I think I got it working by compiling from source, but I'm sure there
> will be others that will appreciate a package RHEL 4.
>
And so I am packaging rubygem-mongrel and dependencies for EL-4, thanks.
Kind regards,
Jeroen van Meeuwen
-kanarip
--~--~-~--~~
Hi
> I'm running RHEL 4, and have just installed Mongrel and Nginx.
>
> I found and have tried this init script:
> http://github.com/duritong/puppet-puppet/tree/master/files/cluster/init.d/puppetmaster.CentOS
>
> Starting puppetmaster works fine, but when I try stopping it I get a "pidof:
> inv
13 matches
Mail list logo
