# Shark PID files in tmp folder?!

**URL:** <https://discuss.elastic.co/t/shark-pid-files-in-tmp-folder/15212>\
**Category:** Elasticsearch\
**Created:** [January 12, 2014, 1:00pm UTC](https://discuss.elastic.co/t/shark-pid-files-in-tmp-folder/15212 "2014-01-12T13:00:02Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Robin\_Verlangen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/robin_verlangen/32/1542_2.png) [@Robin\_Verlangen](https://discuss.elastic.co/u/Robin_Verlangen)\
**Post date:** [January 12, 2014, 1:00pm UTC](https://discuss.elastic.co/t/shark-pid-files-in-tmp-folder/15212/1 "2014-01-12T13:00:02Z")

</div>

Hi there,

We noticed that the Shark PID files are not stored under /var/run , but in  
/tmp which causes problems with shark servers that die every once in a  
while once a cronjob cleans up those folders.

The easiest way of course is for us to update the cron script and update  
shark, however I think the real solution would be to modify the default  
behavior of shark. As it is now using a file in a temporary folder, which  
should not make the application crash once it is being removed.

What do you think?

Best regards,

Robin Verlangen  
_Chief Data Architect_

W [http://www.robinverlangen.nl](http://www.robinverlangen.nl)  
E robin@us2.nl

[http://goo.gl/Lt7BC](http://goo.gl/Lt7BC)  
_What is CloudPelican? [http://goo.gl/HkB3D](http://goo.gl/HkB3D)_

Disclaimer: The information contained in this message and attachments is  
intended solely for the attention and use of the named addressee and may be  
confidential. If you are not the intended recipient, you are reminded that  
the information remains the property of the sender. You must not use,  
disclose, distribute, copy, print or rely on this e-mail. If you have  
received this message in error, please contact the sender immediately and  
irrevocably delete this message and any copies.

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CADVHTB\_FFX%3DK1oOOaZJvrTvtbQL1iGr%3DNaurceWnh2NTB5VPAw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CADVHTB_FFX%3DK1oOOaZJvrTvtbQL1iGr%3DNaurceWnh2NTB5VPAw%40mail.gmail.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\
**Post date:** [January 12, 2014, 1:29pm UTC](https://discuss.elastic.co/t/shark-pid-files-in-tmp-folder/15212/2 "2014-01-12T13:29:07Z")

</div>

Not sure what shark pid files are, but yes, you are right, pid files belong  
under /var/run/ and not /tmp

Jörg

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAKdsXoHcaEts\_rG954vTyAdJVExRZNkGLdM8Vj0R9-Ws\_F2g4w%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoHcaEts_rG954vTyAdJVExRZNkGLdM8Vj0R9-Ws_F2g4w%40mail.gmail.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<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:** [July 6, 2017, 1:57am UTC](https://discuss.elastic.co/t/shark-pid-files-in-tmp-folder/15212/3 "2017-07-06T01:57:15Z")

</div>

Closed on July 6, 2017, 1:57am UTC


