The code should probably look like the statements above it.
Please verify, I just detected it using cppcheck.
Signed-off-by: Thomas Jarosch
---
src/unit.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/unit.c b/src/unit.c
index 903a8e4..c793b11 100644
--- a/src/u
2011/11/9 Michael D. Berger :
> myDaemon must start after myBaseDaemon, and must start only
> if myBaseDaemon is started.
>
> Do I use:
> After=myBaseDaemon
> Requires=myBaseDaemon
> ;or only:
> Requires=myBaseDaemon
> ?
>
> Thanks,
> Mike.
>
The first. Requires alone doesn't ensure the order
Both. Otherwise your daemon can be started in parallel and be done before the
other daemon.
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
"Michael D. Berger" wrote:
myDaemon must start after myBaseDaemon, and must start only
if myBaseDaemon is started.
Do I use:
Afte
myDaemon must start after myBaseDaemon, and must start only
if myBaseDaemon is started.
Do I use:
After=myBaseDaemon
Requires=myBaseDaemon
;or only:
Requires=myBaseDaemon
?
Thanks,
Mike.
--
Michael D. Berger
m.d.ber...@ieee.org
http://www.rosemike.net/
__
2011/11/9 Lennart Poettering :
> On Wed, 09.11.11 08:13, "Jóhann B. Guðmundsson" (johan...@gmail.com) wrote:
>> Do you have any links to documentation on how to autoload kmods on use?
>
> Well, this is a kernel feature. The kernel module developers have to add
> the right directives to their .c so
On Wed, 09.11.11 08:13, "Jóhann B. Guðmundsson" (johan...@gmail.com) wrote:
> On 11/09/2011 01:14 AM, Lennart Poettering wrote:
> >So, ideally all kmods these days can be autoloaded on use. And for the
> >few ones which cannot be autoloaded placing a file in
> >/etc/load-modules.d/
>
> Do you hav
On 11/09/2011 01:14 AM, Lennart Poettering wrote:
So, ideally all kmods these days can be autoloaded on use. And for the
few ones which cannot be autoloaded placing a file in
/etc/load-modules.d/
Do you have any links to documentation on how to autoload kmods on use?
JBG
__
