Hi all,
I've recently updated the RH5 Foreman rpm to include a foreman service (a
wrapper for webrick) and to install sqlite by default.
hopefully making it a bit easier to get it running quickly.
any feedback appreciated:
http://theforeman.org/blogs/show/8-Foreman-rpm
Ohad
--
You received th
It looks to me like yum itself is broken. Try installing something using the
yum command-line client.
On Apr 12, 2010, at 7:24 PM, dbs wrote:
> Okay, I'm stymied. I set up a rule to kick a new .repo file out to
> my
> clients into /etc/yum.repos.d/ called 'lwm.repo'.
>
> The rule says:
> clas
Okay, I'm stymied. I set up a rule to kick a new .repo file out to
my
clients into /etc/yum.repos.d/ called 'lwm.repo'.
The rule says:
class lwm-repos{
file { "/etc/yum.repos.d/lwm.repo" :
owner => "root",
group => "root",
mode => 444,
On Mon, Apr 12, 2010 at 6:46 PM, Ohad Levy wrote:
> Hi,
>
> While its not for the public, I do have a question in the matter, what do
> most people do with id tags?
> I do have this annoying problem that the id changes every now and then (e.g.
> because of the protocol used to checkout the files)
Hi,
While its not for the public, I do have a question in the matter, what do
most people do with id tags?
I do have this annoying problem that the id changes every now and then (e.g.
because of the protocol used to checkout the files) hence changing the file.
I didnt really look into it because
On Mon, Apr 12, 2010 at 2:54 PM, Darvin Denmian wrote:
> Hello,
>
> even removing one double quote I got the same error:
>
> "-":6: bad minute
> errors in crontab file, can't install.
>
> Thanks!
>
> On Mon, Apr 12, 2010 at 6:49 PM, Frank Sweetser wrote:
> > On 04/12/2010 05:45 PM, Darvin Denmian
brain fart!
That obviously wasn't meant to be for a public list :)
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+u
http://b/issue?id=2583243
That bug gives the background as to *why*.
So that clients don't end up all downloading every file at once as the
RCS tags change, I'm proposing to go through modules in *stable*
Puppet configurations and strip them out with the correct $Id$ tags
module by module over th
Hello,
even removing one double quote I got the same error:
"-":6: bad minute
errors in crontab file, can't install.
Thanks!
On Mon, Apr 12, 2010 at 6:49 PM, Frank Sweetser wrote:
> On 04/12/2010 05:45 PM, Darvin Denmian wrote:
>> Hello,
>>
>> Why the following lines doesn't work?
>>
>> cro
On 04/12/2010 05:45 PM, Darvin Denmian wrote:
> Hello,
>
> Why the following lines doesn't work?
>
>cron { "app" :
> command => ""nice -n -10 /usr/bin/php
I'm not familiar with the cron type, but I'm betting that the pair of double
quotes before the nice command isn't helping any =
Hello,
Why the following lines doesn't work?
cron { "app" :
command => ""nice -n -10 /usr/bin/php
/var/www/public_html/rotinas/rotinas.php 2>&1>> /var/log/app.log",
environment => "PATH=$PATH",
user=> root,
hour=> '*',
minute => '*',
Didn't find a bug related to this, I have created:
http://projects.puppetlabs.com/issues/3538
Thanks
On Mon, Apr 12, 2010 at 7:00 AM, Michael DeHaan wrote:
> >> I think you're saying that Puppet isn't comparing installed packages
> >> quite the way yum does, and that yum would be able to find th
On Sun, Apr 11, 2010 at 9:58 PM, Luke Kanies wrote:
> We're very excited to announce that after years of being a critical
> contributor to Puppet, including writing the Puppet Book, James Turnbull is
> joining Puppet Labs as Director of Operations, where he'll be responsible
> for infrastructure,
On Sun, Apr 11, 2010 at 10:58 PM, Luke Kanies wrote:
> We're very excited to announce that after years of being a critical
> contributor to Puppet, including writing the Puppet Book, James Turnbull is
> joining Puppet Labs as Director of Operations, where he'll be responsible
> for infrastructure
For you debian users out there:
Digg has allowed me to release our apt module as open-source. It's
simple, but we find it useful. Contributions and criticisms welcome:
http://github.com/plathrop/libpuppet-apt
Enjoy!
--
You received this message because you are subscribed to the Google Groups
On Sun, Apr 11, 2010 at 08:58:56PM -0700, Luke Kanies wrote:
> Welcome to the company, James.
Congratulations, James! Thanks for all your hard work.
--
Jos Backus
jos at catnook.com
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to t
>> I think you're saying that Puppet isn't comparing installed packages
>> quite the way yum does, and that yum would be able to find the match
>> if executed with just the version and not the release, right?
>
> Yes this is correct. Its all about being less precise in your match.
>
Ok, I agree th
Thank you. I will check this.
Regards
Denny
On 12 Apr., 15:12, James Turnbull wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 12/04/10 11:00 PM, Denny wrote:
>
> > Hi James,
>
> > thank you for your quick reply. I'm running CentOS 5.3 so i have
> > installed the new version from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/04/10 11:00 PM, Denny wrote:
> Hi James,
>
> thank you for your quick reply. I'm running CentOS 5.3 so i have
> installed the new version from
> the epel-repo with "yum install puppet-server".
>
I think you might have some stray 0.24.x files a
Hi James,
thank you for your quick reply. I'm running CentOS 5.3 so i have
installed the new version from
the epel-repo with "yum install puppet-server".
Regards
Denny
On 12 Apr., 14:53, James Turnbull wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 12/04/10 10:41 PM, Denny wrot
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/04/10 10:41 PM, Denny wrote:
> Hi @ all !
> I have updated my puppetserver to version 0.25.4. After testing
> connectivity with older clients (ver. 0.24.8)
> everything looks fine.
> Now, I'm beginning to upgrade these clients. Clients running wi
Hi @ all !
I have updated my puppetserver to version 0.25.4. After testing
connectivity with older clients (ver. 0.24.8)
everything looks fine.
Now, I'm beginning to upgrade these clients. Clients running with ver.
0.25.4, gets the following message on every run: "warning: Puppet.type
is deprecated
Thanks Ohad - I didn't know about foreman. Will have a play :)
On Apr 12, 12:50 pm, Ohad Levy wrote:
> On Mon, Apr 12, 2010 at 5:24 PM, yatesco wrote:
> > I have managed to get puppet deployed on a small cluster of debian
> > (virtual) machines. Very nice tool!
>
> > welcome to the club :)
> >
On Mon, Apr 12, 2010 at 5:24 PM, yatesco wrote:
> I have managed to get puppet deployed on a small cluster of debian
> (virtual) machines. Very nice tool!
>
> welcome to the club :)
> I have a couple of questions, some of which I have found responses
> from google, but just don't understand, ot
Hi all,
I have managed to get puppet deployed on a small cluster of debian
(virtual) machines. Very nice tool!
I have a couple of questions, some of which I have found responses
from google, but just don't understand, others of which I have no idea
at all.
- is there anyway I can get emailed i
On 4/10/2010 10:54 PM, Michael DeHaan wrote:
On Fri, Apr 9, 2010 at 11:48 AM, Gustavo Soares
wrote:
Hi!
I don't know if here is the right place to say this, but the
puppet-dashboard
tour webpage
(http://www.puppetlabs.com/blog/a-tour-of-puppet-dashboard-0-1-0/)
seems to have some broken image l
Excellent news. Congrats James.
On Apr 12, 4:58 am, Luke Kanies wrote:
> We're very excited to announce that after years of being a critical
> contributor to Puppet, including writing the Puppet Book, James
> Turnbull is joining Puppet Labs as Director of Operations, where he'll
> be respon
27 matches
Mail list logo
