Back on-list:
Looks like you're developing for a Red Hat-based distro; I know the
rpmdevtools package in Fedora contains /etc/rpmdevtools/template.init file
that is a great start. Also check out the related wiki page:
http://fedoraproject.org/wiki/FCNewInit/Initscripts
-Doug
On 10/19/2011
Creating your own init script if one is not provided is definitely the best
approach; but failing that, you can still use the service resource as a
glorified exec; I've done this w/ my arpwatch daemon on redhat boxes since
it's otherwise difficult to run multiple arpwatch daemons:
##
# maintains
It might be helpful to include the O/S you're asking about, possibly with
the package... sometimes it's a matter of just changing/adding a
respository. Sometimes it might be a little more involved.
On Tue, Oct 18, 2011 at 1:21 PM, Dan White y...@comcast.net wrote:
Are there any exapmples out
On Tue, Oct 18, 2011 at 08:21:34PM +, Dan White wrote:
Are there any exapmples out there that show an intelligent way to do this ?
http://docs.puppetlabs.com/references/stable/type.html#service
That makes it sound like as long as you have the right init script (or
platform-specific variant
The one thing that I'll mention is that you want to use hasstatus = true
whenever possible, I've found, at least on older versions of Puppet
(0.25.x). Sometimes the logic it tries to use otherwise doesn't quite work,
but using the /etc/init.d/servicename status check seems to work fine.
--
Nathan
Yes, I agree. If it were something as simple as pulling in a binary to the
right location and setting up a script in /etc/init.d to let services/xinitd
run it.
But I am looking for something that might pull in a tar-ball, unroll it,
compile it (maybe) and set up the appripriate stuff.
I can
RHEL 5, and the packages in question come as tar-balls that have to be unrolled
into place and then compiled/configured. Not your simple yum install..., sad
to say.
- Russell Van Tassell russel...@gmail.com wrote:
It might be helpful to include the O/S you're asking about, possibly with
I'm on puppet 2.6.something, and I fully plan to use the
/etc/init.d/servicename mechanism to define my service. Is there any other
(correct) way to do it ?
I'm just looking for an automated way to install it with puppet.
- Nathan Clemons nat...@livemocha.com wrote:
The one thing that
On Tue, Oct 18, 2011 at 08:54:22PM +, Dan White wrote:
Yes, I agree. If it were something as simple as pulling in a binary to the
right location and setting up a script in /etc/init.d to let services/xinitd
run it.
But I am looking for something that might pull in a tar-ball, unroll
I've always thought that if you wanted, consistent, repeatable methodology for
install/remove/upgrade that the native packaging is always the way to go and
rpm-build does exactly that with tarballs.
I don't think Puppet is the way to drop tarballs config make make
install because so many
Use fpm.
On Tue, Oct 18, 2011 at 1:21 PM, Dan White y...@comcast.net wrote:
Are there any exapmples out there that show an intelligent way to do this ?
My searches are not turning up anything useful
“Sometimes I think the surest sign that intelligent life exists elsewhere
in the universe
Thanks for the opinion.
I understand your concern, but I have a need to do exactly that.
Making a long story short, RPM's do not work for this need unless you consider
a relocatable package
http://www.rpm.org/max-rpm/s1-rpm-reloc-building-relocatable.html
and I have seen some serious objections
If it's a straightforward compilation, you should be able to do this with a
set of chained execs.
For instance, a file resource to push the tarball, then an exec to extract
it (which depends on the tarball), an exec to configure it (which depends on
the previous exec), and an exec to install it
13 matches
Mail list logo
