From: Richard Michael <rmichael@edgeofthenet.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: RUN
Date: Wed, 11 Jul 2007 13:12:28 +0000 [thread overview]
Message-ID: <20070711131228.GB10633@server> (raw)
In-Reply-To: <4693ECED.9090209@inguin.com>
> You can have any number of rules with _one_ RUN key per rule and they
> will all be executed.
>
> The question was how to run two programs from a _single_ rule. The
> obvious solution would be to specify two RUN keys, but that doesn't
> work with todays in-memory rule presentation. It will change when I
> find the time to work on that.
That clarifies it, thanks.
Perhaps the man page could indicate:
RUN
If more than one program must be run for an event, a rule with one RUN
key must be written for each program. For example, to run three
programs, write three rules with identical match keys, each running one
of the three programs.
Does that decribe the situation accurately?
Richard
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2007-07-11 13:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-10 20:32 RUN Adam Kane
2007-07-10 22:01 ` RUN Bauke Jan Douma
2007-07-10 22:08 ` RUN Adam Kane
2007-07-11 0:04 ` RUN Kay Sievers
2007-07-11 0:59 ` RUN Richard Michael
2007-07-11 1:08 ` RUN Kay Sievers
2007-07-11 2:11 ` RUN Bryan Kadzban
2007-07-11 8:36 ` RUN Scott James Remnant
2007-07-11 13:12 ` Richard Michael [this message]
2007-07-13 0:10 ` RUN Adam Kane
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=20070711131228.GB10633@server \
--to=rmichael@edgeofthenet.org \
--cc=linux-hotplug@vger.kernel.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 NNTP newsgroup(s).