Micah Anderson wrote:
>> b) The Debian default in the versions so far which tried /once/ and then
>>exited without looping *at all*. That was what puppet <= 0.24 did
>>with "-w 0" and that's what the documentation still (incorrectly)
>>says.
>
> Doyou have a reference, or a commitsh wh
* Faidon Liambotis [2009-01-14 17:13-0500]:
> Thom May wrote:
> > On Tue, Jan 13, 2009 at 4:26 PM, Faidon Liambotis
> > wrote:
> >> Thijs Kinkhorst wrote:
> >> Sometimes people just install a package to read documentation/the
> >> manpages/read the code etc.
> >>
> >> It should either need manua
Thom May wrote:
> On Tue, Jan 13, 2009 at 4:26 PM, Faidon Liambotis wrote:
>> Thijs Kinkhorst wrote:
>> Sometimes people just install a package to read documentation/the
>> manpages/read the code etc.
>>
>> It should either need manual work for the init script to start (i.e.
>> disable autostart)
package puppet
severity 509566 wishlist
kthxbye
On Tue, Jan 13, 2009 at 4:26 PM, Faidon Liambotis wrote:
> Thijs Kinkhorst wrote:
> Sometimes people just install a package to read documentation/the
> manpages/read the code etc.
>
> It should either need manual work for the init script to start (i
Thijs Kinkhorst wrote:
>> FWIW, I don't agree. I don't find it acceptable to have a
>> fresh-installed package writing 2 lines on my syslog every 5 seconds.
>
> Busylooping is obviously wrong, but doing it every 5 seconds is not an
> unacceptable burden. It does not load the system significantly.
On Thu, January 8, 2009 14:10, Faidon Liambotis wrote:
> Thijs Kinkhorst wrote:
>
>>> Setting waitforcert to "5" helps a bit, but it is still a problem
>>> IMO.
>> Your suggestions are all very valid in my opinion, but I think that the
>> uploaded fix has made the issue not grave anymore. I hope
Thom May wrote:
> I'm not sure what I want to do, and I definitely don't want you to NMU.
ACK.
I don't want to challenge you on this (and I won't act) but please
reconsider the severity of this.
Thanks,
Faidon
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subjec
On Thu, Jan 8, 2009 at 8:10 AM, Faidon Liambotis wrote:
> I will happily NMU if you agree with me but don't have the time for an
> upload.
I'm not sure what I want to do, and I definitely don't want you to NMU.
Thanks,
-Thom
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.o
Thijs Kinkhorst wrote:
>> Setting waitforcert to "5" helps a bit, but it is still a problem IMO.
>
> Your suggestions are all very valid in my opinion, but I think that the
> uploaded fix has made the issue not grave anymore. I hope the Puppet
> maintainers will evaluate your suggestions for inclu
severity 509566 normal
thanks
> found 509566 0.24.5-3
> found 509566 0.24.6-1
> thanks
> Setting waitforcert to "5" helps a bit, but it is still a problem IMO.
Your suggestions are all very valid in my opinion, but I think that the
uploaded fix has made the issue not grave anymore. I hope the Pu
found 509566 0.24.5-3
found 509566 0.24.6-1
thanks
Hi,
Setting waitforcert to "5" helps a bit, but it is still a problem IMO.
Actually, I think the bug lies in the code, and not in the configuration.
The manpage mentions
"You can turn off waiting for certificates by specifying a time of 0."
a
severity 509566 grave
thanks
Besides having autosign disabled on the master or not having network at
all, the problem can be manifested with installing the package on a
random on a random network.
Let me repeat this: executing
apt-get install puppet
on *any* random system, without any pri
Package: puppet
Version: 0.24.5-2
Severity: normal
puppetd accepts a "timeout" argument (-w), that instructs the daemon to wait
for a specified amount of time before re-requesting a certificate from the
puppet master. The parameter's value in /etc/default/puppet is set to 0, which
causes puppet to
13 matches
Mail list logo
