Advanced Deployments - Implementing Splunk: Big Data Reporting and Development for Operational Intelligence - page 354

Or, if you plan to overlay an app that contains deploymentclient.conf , you can
forego starting Splunk until that app has been copied into place, as follows:
msiexec.exe /i splunk-xxx.msi AGREETOLICENSE=Yes LAUNCHSPLUNK=0 /quiet
There are options available to start reading data immediately, but I would advise
deploying input configurations to your servers instead of enabling inputs via
installation arguments.
Adding a base configuration
If you are using Splunk's deployment server, this is the time to set up
deploymentclient.conf . This can be accomplished in several ways as follows:
• On the command line by running the following code:
$SPLUNK_HOME/bin/splunk set deploy-poll
deployment_server_name:8089
• By placing a deploymentclient.conf in
$SPLUNK_HOME/etc/system/local/
• By placing an app containing deploymentclient.conf in
$SPLUNK_HOME/etc/apps/
The third option is what I would recommend because it allows overriding this
configuration via a deployment server at a later time. We will work through an
example later in the Using Splunk deployment server section.
If you are deploying configurations in some other way, for instance with puppet, be
sure to restart the Splunk forwarder processes after deploying the new configuration.
Configuring Splunk to launch at boot
On Windows machines, Splunk is installed as a service that will start after
installation and on reboot.
On Unix hosts, the splunk command line provides a way to create startup scripts
appropriate for the operating system you are using. The command looks like this:
$SPLUNK_HOME/bin/splunk enable boot-start
To run Splunk as another user, provide the flag -user , as follows:
$SPLUNK_HOME/bin/splunk enable boot-start -user splunkuser