From: "Canek Peláez Valdés" <caneko@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] looking for a couple of systemd units
Date: Fri, 30 Aug 2013 00:35:10 -0500 [thread overview]
Message-ID: <CADPrc80tyNcDic4CYoM1JowYJQn6j9RStdS2GkWDA4k9S5+Cpg@mail.gmail.com> (raw)
In-Reply-To: <87wqn3wy1g.fsf@einstein.gmurray.org.uk>
On Fri, Aug 30, 2013 at 12:24 AM, Graham Murray <graham@gmurray.org.uk> wrote:
> "Stefan G. Weichinger" <lists@xunil.at> writes:
>
>> Just found this note from Pacho on planet.gentoo.org:
>>
>> http://my.opera.com/pacho/blog/2013/08/27/how-to-write-proper-systemd-unit-files
>>
>> I will have to review some of my files then ;-)
>
> What I did not understand from reading that is why he (or gentoo policy)
> does not like 'type=forking'. Reading the systemd man files, I thought
> that type=forking would be the "natural" choice for most daemons.
On the contrary; with Type=simple systemd has better control on the
service, since systemd itself execv() the service binary, and it can
know precisely its PID and when it finishes. With Type=forking systemd
has to guess what the PID is, and therefore it nees more work to know
the status of the service. It does a pretty good job, but it's easier
with Type=simple.
Type=forking is there for old daemons that don't have a --foreground
or similar option.
Regards.
--
Canek Peláez Valdés
Posgrado en Ciencia e Ingeniería de la Computación
Universidad Nacional Autónoma de México
next prev parent reply other threads:[~2013-08-30 5:35 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-27 3:52 [gentoo-user] looking for a couple of systemd units covici
2013-08-27 4:06 ` Canek Peláez Valdés
2013-08-27 4:18 ` Canek Peláez Valdés
2013-08-27 6:10 ` covici
2013-08-27 6:24 ` Canek Peláez Valdés
2013-08-27 6:46 ` covici
2013-08-27 7:46 ` covici
2013-08-27 13:58 ` Canek Peláez Valdés
2013-08-27 14:41 ` covici
2013-08-27 14:47 ` Canek Peláez Valdés
2013-08-27 15:39 ` covici
2013-08-27 15:57 ` Canek Peláez Valdés
2013-08-27 20:12 ` covici
2013-08-27 14:16 ` Samuli Suominen
2013-08-27 5:41 ` covici
2013-08-27 15:55 ` Stefan G. Weichinger
2013-08-27 16:02 ` Canek Peláez Valdés
2013-08-27 16:16 ` Stefan G. Weichinger
2013-08-27 16:30 ` Canek Peláez Valdés
2013-08-27 16:35 ` Stefan G. Weichinger
2013-08-27 16:40 ` Stefan G. Weichinger
2013-08-27 16:46 ` Stefan G. Weichinger
2013-08-27 16:57 ` Canek Peláez Valdés
2013-08-27 17:32 ` Stefan G. Weichinger
2013-08-28 6:51 ` Stefan G. Weichinger
2013-08-30 5:24 ` Graham Murray
2013-08-30 5:35 ` Canek Peláez Valdés [this message]
2013-08-27 17:27 ` Stefan G. Weichinger
2013-08-27 17:31 ` Stefan G. Weichinger
2013-08-27 18:12 ` Stefan G. Weichinger
2013-08-27 18:15 ` Canek Peláez Valdés
2013-08-27 18:30 ` Stefan G. Weichinger
2013-08-27 18:29 ` Stefan G. Weichinger
2013-08-27 18:38 ` Stefan G. Weichinger
2013-08-27 20:42 ` Stefan G. Weichinger
2013-08-27 20:52 ` covici
2013-08-27 21:04 ` Stefan G. Weichinger
2013-08-28 6:03 ` Stefan G. Weichinger
2013-08-28 6:08 ` Stefan G. Weichinger
2013-08-27 20:24 ` covici
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=CADPrc80tyNcDic4CYoM1JowYJQn6j9RStdS2GkWDA4k9S5+Cpg@mail.gmail.com \
--to=caneko@gmail.com \
--cc=gentoo-user@lists.gentoo.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