<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Custom installations... in Installation</title>
    <link>https://community.splunk.com/t5/Installation/Custom-installations/m-p/64220#M1013</link>
    <description>&lt;P&gt;Our solution to this was to make our own rpm that is dependent upon the &lt;CODE&gt;splunkforwarder&lt;/CODE&gt; RPM.  Our RPM ships the appropriate config files to get a forwarder properly configured and talking to a deployment server.&lt;/P&gt;

&lt;P&gt;Our RPM contains (relative to /opt/splunkforwarder)&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;etc/system/local/user-seed.conf
etc/system/local/server.conf
etc/system/local/deploymentclient.conf
etc/system/local/inputs.conf
etc/auth/server.pem
etc/auth/cacert.pem
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;There is a postinst script that goes along with it to enable boot-start and start splunk for the first time.  &lt;/P&gt;

&lt;P&gt;The most elegant part of this is that an upgrade to the base Splunk RPM won't replace any of these.  I would recommend this approach over trying to spin your own Splunk RPM.&lt;/P&gt;</description>
    <pubDate>Sat, 23 Jul 2011 19:21:55 GMT</pubDate>
    <dc:creator>dwaddle</dc:creator>
    <dc:date>2011-07-23T19:21:55Z</dc:date>
    <item>
      <title>Custom installations...</title>
      <link>https://community.splunk.com/t5/Installation/Custom-installations/m-p/64219#M1012</link>
      <description>&lt;P&gt;Based on the splunk documentation, I'm guessing it's recommended to script customized installation requirements rather than trying to generate a custom RPM.  I'd like some feedback on that.  If customizing RPM's is doable can you post a spec file for 4.2.  I am aware there are spec files for older versions on the net, I'm specifically trying to work with 4.2.  TIA.&lt;/P&gt;</description>
      <pubDate>Tue, 22 Mar 2011 04:23:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/Custom-installations/m-p/64219#M1012</guid>
      <dc:creator>DTERM</dc:creator>
      <dc:date>2011-03-22T04:23:27Z</dc:date>
    </item>
    <item>
      <title>Re: Custom installations...</title>
      <link>https://community.splunk.com/t5/Installation/Custom-installations/m-p/64220#M1013</link>
      <description>&lt;P&gt;Our solution to this was to make our own rpm that is dependent upon the &lt;CODE&gt;splunkforwarder&lt;/CODE&gt; RPM.  Our RPM ships the appropriate config files to get a forwarder properly configured and talking to a deployment server.&lt;/P&gt;

&lt;P&gt;Our RPM contains (relative to /opt/splunkforwarder)&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;etc/system/local/user-seed.conf
etc/system/local/server.conf
etc/system/local/deploymentclient.conf
etc/system/local/inputs.conf
etc/auth/server.pem
etc/auth/cacert.pem
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;There is a postinst script that goes along with it to enable boot-start and start splunk for the first time.  &lt;/P&gt;

&lt;P&gt;The most elegant part of this is that an upgrade to the base Splunk RPM won't replace any of these.  I would recommend this approach over trying to spin your own Splunk RPM.&lt;/P&gt;</description>
      <pubDate>Sat, 23 Jul 2011 19:21:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/Custom-installations/m-p/64220#M1013</guid>
      <dc:creator>dwaddle</dc:creator>
      <dc:date>2011-07-23T19:21:55Z</dc:date>
    </item>
  </channel>
</rss>

