Bug#791412: systemd invoking a service on its own

[Michael Biebl]

Am 04.07.2015 um 20:31 schrieb Ritesh Raj Sarraf:
> On Saturday 04 July 2015 11:43 PM, Michael Biebl wrote:
>>>> But please feel free to reassign back, in case I'm wrong.
>>>>
>> It would help if you explained why this is supposed to be a bug in
>> systemd, it would help
> 
> 
> I really don't have enough pointers to confidently say that it *is* a
> bug in systemd.
> 
> The only point I can make is that it used to work fine with SysV init.
> But that is the past.
> 
> Other point I can see is that the invoking process is systemd.

Well, sure, if  a service start is triggered, the invoking process will
be systemd. That is not a bug though.

It's still unclear to me what the bug in systemd is supposed to be.


> systemd is new, and I am hoping you guys are the right contact to help
> me conclude.
> 
> 
> From within LMT, we background another script, lm-polling-daemon. This
> script is backgrounded after we acquire a lock in the main program i.e.
> /usr/sbin/laptop_mode, and not released until the polling daemon is killed.
> 
> 
> How is systemd/cgroup supposed to handle scripts that background other
> scripts ?

Why do you need all those background/looping/locking etc?

If it is to assure, that only a single process is started, even when you
have multiple start requests at the same time, you get that for free
already under systemd.

It seems to me, that you are trying to work against systemd and not use
the features it provides.


Michael


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20150704/1b52d7b0/attachment-0002.sig>