From: Patrick Williams <patrick@stwcx.xyz>
To: Matt Spinler <mspinler@linux.vnet.ibm.com>
Cc: Joel Stanley <joel@jms.id.au>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: Starting the phosphor-hwmon service from udev rules
Date: Mon, 28 Nov 2016 20:42:16 -0600 [thread overview]
Message-ID: <20161129024216.GS15757@heinlein.lan> (raw)
In-Reply-To: <32e4f53c-5bab-55ba-50f2-25ba891d4127@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 664 bytes --]
On Mon, Nov 28, 2016 at 10:31:20AM -0600, Matt Spinler wrote:
> The command line in the unit file would then somehow make a
> udevadm call to pull out the ENVFILE so it can get passed into the
> executable along with the device path.
This was a detail I missed before. systemd service files natively have
the variable 'ENVFILE'. If they don't automatically take the ENVFILE
from the environment (via udev invocation) then I would rather we use
unique systemd service files instead of unique udev rules. Having the
systemd service file launch some kind of piped shell processing is
problematic and certainly not preferred.
--
Patrick Williams
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2016-11-29 2:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-28 16:31 Starting the phosphor-hwmon service from udev rules Matt Spinler
2016-11-29 1:28 ` Joel Stanley
2016-11-29 2:39 ` Patrick Williams
2016-11-29 2:42 ` Patrick Williams [this message]
2016-11-29 16:30 ` Matt Spinler
2016-11-30 1:14 ` Andrew Jeffery
2016-11-30 2:19 ` Patrick Williams
2016-12-07 19:44 ` Matt Spinler
2016-12-07 22:38 ` Patrick Williams
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=20161129024216.GS15757@heinlein.lan \
--to=patrick@stwcx.xyz \
--cc=joel@jms.id.au \
--cc=mspinler@linux.vnet.ibm.com \
--cc=openbmc@lists.ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.