https://community.splunk.com/t5/Deployment-Architecture/Splunk-configuration-changes-SIGHUP-or-restart/m-p/9123#M2 <P>In general, settings which affect search take effect immediately, since searches are run in a separate process that reloads configurations. These settings include lookup tables, field extractions, tags and eventtypes.</P> <P>Settings which affect indexing usually require a restart. These include index time field extractions, timestamp properties and index creation.</P> <P>Input settings made through the UI and CLI do not require restarts and take place immediately.</P> <P>Splunk doesn't yet support SIGHUP on unix systems, but that is certainly a commonly desired feature.</P> Fri, 15 Jan 2010 05:10:38 GMT Stephen_Sorkin 2010-01-15T05:10:38Z https://community.splunk.com/t5/Deployment-Architecture/Splunk-configuration-changes-SIGHUP-or-restart/m-p/9122#M1 <P>Sometimes I make changes to my Splunk server's configuration, but I do not want to restart Splunk. </P> <P>Which configuration changes require a restart, and which do not?</P> <P>Also, does Splunk support a SIGHUP on linux/unix systems?</P> Fri, 15 Jan 2010 03:13:52 GMT https://community.splunk.com/t5/Deployment-Architecture/Splunk-configuration-changes-SIGHUP-or-restart/m-p/9122#M1 araitz 2010-01-15T03:13:52Z https://community.splunk.com/t5/Deployment-Architecture/Splunk-configuration-changes-SIGHUP-or-restart/m-p/9123#M2 <P>In general, settings which affect search take effect immediately, since searches are run in a separate process that reloads configurations. These settings include lookup tables, field extractions, tags and eventtypes.</P> <P>Settings which affect indexing usually require a restart. These include index time field extractions, timestamp properties and index creation.</P> <P>Input settings made through the UI and CLI do not require restarts and take place immediately.</P> <P>Splunk doesn't yet support SIGHUP on unix systems, but that is certainly a commonly desired feature.</P> Fri, 15 Jan 2010 05:10:38 GMT https://community.splunk.com/t5/Deployment-Architecture/Splunk-configuration-changes-SIGHUP-or-restart/m-p/9123#M2 Stephen_Sorkin 2010-01-15T05:10:38Z https://community.splunk.com/t5/Deployment-Architecture/Splunk-configuration-changes-SIGHUP-or-restart/m-p/9124#M3 <P>Heehee sending splunk a SIGHUP causes it to shut down. So you probably don't want to do this.</P> Thu, 11 Mar 2010 17:13:37 GMT https://community.splunk.com/t5/Deployment-Architecture/Splunk-configuration-changes-SIGHUP-or-restart/m-p/9124#M3 jrodman 2010-03-11T17:13:37Z https://community.splunk.com/t5/Deployment-Architecture/Splunk-configuration-changes-SIGHUP-or-restart/m-p/9125#M4 <P>See also<BR /> <A href="http://splunk-base.splunk.com/answers/24807/what-changes-to-configuration-files-require-a-restart-of-splunk">http://splunk-base.splunk.com/answers/24807/what-changes-to-configuration-files-require-a-restart-of-splunk</A></P> Wed, 01 Jun 2011 17:56:06 GMT https://community.splunk.com/t5/Deployment-Architecture/Splunk-configuration-changes-SIGHUP-or-restart/m-p/9125#M4 lguinn2 2011-06-01T17:56:06Z