public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Chris Brannon <chris@the-brannons.com>
To: "Speakup is a screen review system for Linux."
	<speakup@linux-speakup.org>
Subject: Re: espeakup release coming soon
Date: Wed, 20 Jul 2016 17:07:26 -0700	[thread overview]
Message-ID: <87oa5r26rl.fsf@mushroom.localdomain> (raw)
In-Reply-To: <20160720233531.GC4169@var.home> (Samuel Thibault's message of "Thu, 21 Jul 2016 01:35:31 +0200")

Samuel Thibault <samuel.thibault@ens-lyon.org> writes:

> currently espeakup uses daemon() to do the daemonizing stuff.
> Unfortunately, daemon() does things not very appropriately, and there
> is notably a delay between the parent exit()ing and the child writing
> the pid file.

Why not just use the -d option when starting espeakup?
This causes it to stay in the foreground.  No pid file is written, etc.
The long option name is --debug.  I'd argue that that is a bit of a
misnomer, since all it really does is cause espeakup to stay in the
foreground.  Maybe it should have been called --dontfork instead.
I thought systemd preferred non-forking daemons?
Anyway, -d is what I use to run espeakup under runit, and it has worked
well in practice for over a year.

-- Chris

  reply	other threads:[~ UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 William Hubbs
 ` Jude DaShiell
   ` William Hubbs
   ` Samuel Thibault
     ` Chris Brannon [this message]
       ` Samuel Thibault
         ` Chris Brannon
           ` Samuel Thibault
     ` Mark Peveto
       ` Samuel Thibault
         ` Mark Peveto
           ` Chris Brannon
           ` Samuel Thibault
 ` Samuel Thibault
   ` William Hubbs
     ` Samuel Thibault
   ` William Hubbs

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87oa5r26rl.fsf@mushroom.localdomain \
    --to=chris@the-brannons.com \
    --cc=speakup@linux-speakup.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).