官术网_书友最值得收藏!

Starting on reboot

By default, Splunk does not start when the server is rebooted; you will typically want it to do so. You can have Splunk create a script that starts it by executing an 'enable boot-start' command (as root, as this will alter OS level files):

[root@ip-172-31-28-164 ~]# cd /opt/splunk/bin
[root@ip-172-31-28-164 bin]# ./splunk enable boot-start -user splunk
Init script installed at /etc/init.d/splunk.
Init script is configured to run at boot.

Then, edit the /etc/init.d/splunk file and add USER=splunk right after the RETVAL=0 entry near the top of the file:

#!/bin/sh
#
# /etc/init.d/splunk
# init script for Splunk.
# generated by 'splunk enable boot-start'.
#
# chkconfig: 2345 90 60
# description: Splunk indexer service
#
RETVAL=0
USER=splunk

. /etc/init.d/functions

splunk_start() {
echo Starting Splunk...
"/opt/splunk/bin/splunk" start --no-prompt --answer-yes
RETVAL=$?
[ $RETVAL -eq 0 ] andand touch /var/lock/subsys/splunk
}
...
Be sure to specify   -user splunk when you execute the enable boot-start command, and make the noted change to the /etc/init.d/splunk file, or the script will start Splunk as root upon startup and cause you all kinds of file ownership issues! You can verify that Splunk is running as the splunk user by executing the:  ps -ef | grep splunk command and checking to see which user (root or splunk) owns the splunk processes. If you   DO  accidentally start splunk as root, stop Splunk, cd to the   /opt
/splunk
 directory, and run  chown -R splunk:splunk ./  (as root) to change the ownership of all the files back to the splunk user. Don't fret—we've all done it, and it's easily fixed.

主站蜘蛛池模板: 西峡县| 绿春县| 同德县| 上思县| 南川市| 枣强县| 高安市| 兴和县| 和林格尔县| 民县| 天津市| 富裕县| 通州市| 邻水| 永胜县| 康马县| 遵义县| 延庆县| 福海县| 沙湾县| 井冈山市| 深州市| 海林市| 司法| 高青县| 九寨沟县| 卓尼县| 焦作市| 繁峙县| 会昌县| 乾安县| 石柱| 南江县| 仪陇县| 昌乐县| 九台市| 肇州县| 福清市| 馆陶县| 建宁县| 西林县|