https://community.splunk.com/t5/Splunk-Search/Multiple-instances-of-Splunk-w-Boot-start/m-p/103499#M183074 <P>You could run the './splunk enable boot-start' command on the first instance of splunk, then just rename your /etc/init.d script to something like "splunk1" or "splunk2" or something like that, then run chkconfig -add <SCRIPT-NAME> (e.g. chkconfig -add splunk1...that will create all the symbolic links in the rcx.d folders and perform all the other magic. Then, you can move to the next instance and run ./splunk enable boot-start on this instance and rename it again...etc. Basically, every instance will edit/overwrite the script /etc/init.d/splunk...so plan accordingly.</SCRIPT-NAME></P> <P>You could also edit the /etc/init.d/splunk script, I suppose...but that seems more error-prone.</P> Tue, 17 May 2011 20:34:45 GMT cgilbert_splunk 2011-05-17T20:34:45Z https://community.splunk.com/t5/Splunk-Search/Multiple-instances-of-Splunk-w-Boot-start/m-p/103498#M183073 <P>How can I have multiple splunk instances on linux and use boot-start? The command "./splunk enable boot-start" will over-write the previous startup script in /etc/init.d</P> Tue, 17 May 2011 20:30:47 GMT https://community.splunk.com/t5/Splunk-Search/Multiple-instances-of-Splunk-w-Boot-start/m-p/103498#M183073 magicfletch 2011-05-17T20:30:47Z https://community.splunk.com/t5/Splunk-Search/Multiple-instances-of-Splunk-w-Boot-start/m-p/103499#M183074 <P>You could run the './splunk enable boot-start' command on the first instance of splunk, then just rename your /etc/init.d script to something like "splunk1" or "splunk2" or something like that, then run chkconfig -add <SCRIPT-NAME> (e.g. chkconfig -add splunk1...that will create all the symbolic links in the rcx.d folders and perform all the other magic. Then, you can move to the next instance and run ./splunk enable boot-start on this instance and rename it again...etc. Basically, every instance will edit/overwrite the script /etc/init.d/splunk...so plan accordingly.</SCRIPT-NAME></P> <P>You could also edit the /etc/init.d/splunk script, I suppose...but that seems more error-prone.</P> Tue, 17 May 2011 20:34:45 GMT https://community.splunk.com/t5/Splunk-Search/Multiple-instances-of-Splunk-w-Boot-start/m-p/103499#M183074 cgilbert_splunk 2011-05-17T20:34:45Z https://community.splunk.com/t5/Splunk-Search/Multiple-instances-of-Splunk-w-Boot-start/m-p/103500#M183075 <P>There is a pid file mentioned in the script that should be modified in the second script, no?</P> Mon, 22 Aug 2011 19:20:30 GMT https://community.splunk.com/t5/Splunk-Search/Multiple-instances-of-Splunk-w-Boot-start/m-p/103500#M183075 vbumgarner 2011-08-22T19:20:30Z https://community.splunk.com/t5/Splunk-Search/Multiple-instances-of-Splunk-w-Boot-start/m-p/103501#M183076 <P>Careful with the syntax here as chkconfig expects <STRONG>--</STRONG>add </P> <BLOCKQUOTE> <P>chkcnfig --add</P> </BLOCKQUOTE> <P>It's interesting to note that by using </P> <BLOCKQUOTE> <P>chkconfig --list </P> </BLOCKQUOTE> <P>you may check that you've gotten all the scripts you need configured as planned.</P> Tue, 28 Jul 2015 19:11:29 GMT https://community.splunk.com/t5/Splunk-Search/Multiple-instances-of-Splunk-w-Boot-start/m-p/103501#M183076 Stefan 2015-07-28T19:11:29Z