I had this strange error after the first in resolv.conf registered (internal)
dns-server died. After a restart of the dns-server the error was gone.
On 06.05.2012, at 03:51, Sans wrote:
Dear all,
I'm getting this really annoying problem, where it's being failed
intermittently. The errors
Why would you like to do this? With the following service provider (as a
sample) openvpn would be restarted if the service is in a maintenance state (if
possible) or disabled. Or do I miss your point?
service { 'openvpn':
ensure= running,
provider = smf,
enable= true,
You can use a define:
define perl::installCPAN () {
exec { cpan_install_$name:
command = /usr/bin/cpan -i \$name\,
timeout = 600,
unless = perl -e \use $name\,
require = Package['perl'],
}
}
On 27.09.2011, at 16:59, Jeffrey Ollie wrote:
Google searches don't turn up
Maybe using rvm makes your gem live easier. You can use different gemsets, per
user.
rvm.beginrescueend.com
On 20.01.2011, at 05:02, John Warburton wrote:
Hi
I have a small number of gems I install on my puppet server, and manage to
get them compiled and they pick up my non standard
Felix,
If you run puppetd from /etc/init.d, you may want to tweak its
environment right in its init Script.
Nexenta is using SMF like Solaris, not init.d like Linux.
In any case, be sure to create a suitable environment. Puppet cannot
do
that for you (afaik).
Yes that is right. And my
Nexenta is using SMF like Solaris, not init.d like Linux.
Uhm, my bad. My knowledge on Solaris is obviously limited; you may
want
to ask the Solaris folks how to do what you need to do.
Yes of course I will. It would make it easier to explain if I knew how
puppet is executing system
I am using puppet 2.6 with Nexenta ncp 3.0.1 - an OpenSolaris distro
with Ubuntu userland. Most things work great, only a few make trouble.
A big problem is creating a (Solaris-) Zone with Puppet. It does not
work with puppetmasterd only if run it with puppet manually:
puppet --debug
On 16.09.2010, at 11:31, Ben Tullis wrote:
Are old reports purged at any time, or will they hang about for ever?
Our dashboard_production.reports table now contains ~380,000 entries
and
consumes 814MB of disk space. Would it help to prune these to a
certain
time-period?
Rails logs are
