# Logstash re-register on POSIX SIG

**URL:** <https://discuss.elastic.co/t/logstash-re-register-on-posix-sig/102558>\
**Category:** Logstash\
**Created:** [October 3, 2017, 1:03pm UTC](https://discuss.elastic.co/t/logstash-re-register-on-posix-sig/102558 "2017-10-03T13:03:21Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Conall\_Prendergast](https://avatars.discourse-cdn.com/v4/letter/c/d26b3c/32.png) [@Conall\_Prendergast](https://discuss.elastic.co/u/Conall_Prendergast)\
**Post date:** [October 3, 2017, 1:03pm UTC](https://discuss.elastic.co/t/logstash-re-register-on-posix-sig/102558/1 "2017-10-03T13:03:21Z")

</div>

Logstash will listen for a SIGHUP and reload the configuration file when it receives one.  
It listens for SIGSTP and will safely shutdown the pipeline.

Is there a way to get logstash to re-register a plugin by giving it a specific signal? Can I trap a signal in a logstash plugin like this?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [October 31, 2017, 1:03pm UTC](https://discuss.elastic.co/t/logstash-re-register-on-posix-sig/102558/2 "2017-10-31T13:03:42Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.