Skip to main content

Timeline for Init Scripts: Do I Need a PID File?

Current License: CC BY-SA 3.0

12 events
when toggle format what by license comment
Jul 3, 2020 at 8:04 history bumped CommunityBot This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Feb 28, 2020 at 14:02 history bumped CommunityBot This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Oct 19, 2019 at 20:01 history bumped CommunityBot This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Jun 14, 2019 at 20:02 history bumped CommunityBot This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Feb 10, 2019 at 6:00 history bumped CommunityBot This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Nov 10, 2015 at 1:49 comment added cas actually, PID files come from sysvinit only starting services and not keeping track of them afterwards. sysvinit is every bit as flexible as upstart or systemd...but its design criteria is much simpler, from a simpler age. PID files exist to help other tools (or the admin on the command line) keep track of and manage daemons after they've been started.
Nov 9, 2015 at 14:31 answer added cristi timeline score: 1
Nov 9, 2015 at 14:28 comment added jordanm You can avoid this hassle if your OS supports upstart jobs (Ubuntu, Centos 6) or Systemd (Debian, Centos 7).
Nov 9, 2015 at 14:21 history edited Raphael Ahrens CC BY-SA 3.0
removed the text that is irrelevant for the question
Nov 9, 2015 at 14:19 history edited azurepancake CC BY-SA 3.0
added 82 characters in body
Nov 9, 2015 at 14:12 review First posts
Nov 9, 2015 at 14:21
Nov 9, 2015 at 14:11 history asked azurepancake CC BY-SA 3.0