Le vendredi 6 février 2015, 21:23:14 Mantas Mikulėnas a écrit :
> On Fri, Feb 6, 2015 at 5:26 PM, George Karakougioumtzis <
> mad-proffes...@hotmail.com> wrote:
>
> > Hi. Congrats for the near perfect job on systemd! I was searching for a
> > directive to execute a script upon systemd service fail
Interesting point, thanks for the clarifications. I thought that it
would be as simple as setting the environmental variables
DBUS_SESSION_BUS_ADRESS and DISPLAY at each unit file that you would
want to receive notifications from.I thought that i might have not seen
all the directives of systemd an
Trying to use systemd-run with certain properties consistently fails, e.g.:
$ systemd-run --scope --nice 18 --property=NoNewPrivileges=true echo test
Unknown assignment NoNewPrivileges=true.
Failed to create bus message: No such device or address
$ systemd-run --scope --user --nice 18 -p User=nob
Object path components must start with [A-Za-z_] (AFAIK).
Also the value of 'p' is undefined if asprintf fails.
Compare to user_bus_path() in src/login/logind-user-dbus.c:281.
---
src/network/networkd-link-bus.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/src/network/n
On 6 February 2015 at 17:29, Didier Roche wrote:
> Le 05/02/2015 17:11, Dimitri John Ledkov a écrit :
>>
>> Some context for this patch.
>
>
> Hey Dimitri, thanks for working on that. I'm just giving a broader context
> for everyone who followed the past discussion we had in december/january.
>
>
On Fri, Feb 6, 2015 at 5:26 PM, George Karakougioumtzis <
mad-proffes...@hotmail.com> wrote:
> Hi. Congrats for the near perfect job on systemd! I was searching for a
> directive to execute a script upon systemd service failure. I would like
> to receive desktop notifications about such failures.
Le 05/02/2015 17:11, Dimitri John Ledkov a écrit :
Some context for this patch.
Hey Dimitri, thanks for working on that. I'm just giving a broader
context for everyone who followed the past discussion we had in
december/january.
This is a followup on our discussion and what we discussed on
Good afternoon. I have some errors in the boot sequence of a newly built
system:
I see:
systemd[1]: Unit type .busname is not supported on this system.
then later on:
systemd-networkd[278]: Assertion 'bus' failed at
src/libsystemd/sd-bus/bus-util.c:105, function
bus_event_loop_with_idle
Hi. Congrats for the near perfect job on systemd! I was searching for a
directive to execute a script upon systemd service failure. I would like
to receive desktop notifications about such failures. I stumbled upon
OnFailure and FailureAction but these have hardcoded list of actions?
Any hints how
Set proper kdbus_cmd_list object size, otherwise:
dbus-send --system --dest=org.freedesktop.DBus --type=method_call \
print-reply / org.freedesktop.DBus.ListQueuedOwners
string:org.freedesktop.systemd1
Error org.freedesktop.DBus.Error.InvalidArgs: Invalid argument
diff --git a/src/bus-proxyd/dr
---
src/core/load-fragment.c | 14 --
1 file changed, 4 insertions(+), 10 deletions(-)
diff --git a/src/core/load-fragment.c b/src/core/load-fragment.c
index 90bf563..6108d12 100644
--- a/src/core/load-fragment.c
+++ b/src/core/load-fragment.c
@@ -1203,21 +1203,15 @@ int config_parse_
On Mon, Feb 02, 2015 at 03:10:37PM +0100, Zbigniew Jędrzejewski-Szmek wrote:
> On Mon, Feb 02, 2015 at 11:56:39AM +0100, Martin Pitt wrote:
> > Zbigniew Jędrzejewski-Szmek [2015-01-31 20:20 +0100]:
> > > I think the implementation is fine, since it is rather trivial, but I'm
> > > less certain abou
Michael Biebl wrote on 04/02/15 19:59:
> 2015-02-04 13:42 GMT+01:00 Lennart Poettering :
>>> Hello all,
>>>
>>> a little while ago, Jon Severinsson wrote a sysv generator
>>> optimization to not go through all the parsing of init.d scripts and
>>> creation of units if there already is a native unit
On Fri, Feb 6, 2015 at 2:02 PM, Simon McVittie <
simon.mcvit...@collabora.co.uk> wrote:
> On 06/02/15 03:32, 张洋 wrote:
>
>> dbus-daemon --session --print-address --fork > /tmp/session_amgr
>>
>
> This is a security flaw (the search keywords to look for are "symlink
> attack").
>
True, although sy
On 06/02/15 03:32, 张洋 wrote:
dbus-daemon --session --print-address --fork > /tmp/session_amgr
This is a security flaw (the search keywords to look for are "symlink
attack").
export DBUS_SESSION_BUS_ADDRESS=`cat /tmp/session_amgr`
This only affects the environment of the shell script that
Two years ago I raised a query about bind mounting a subdirectory on top
of its parent mount point. I supplied a patch to allow this; it was
discussed but wasn't accepted.
At that time, there was talk about implementing a "BindSubdir" option to
systemd.mount but I don't think anything ever came o
Hello all,
this update now uses the logic from src/shared/install.h, and also
documents the rationale better: The primary reason is to actually
respect a disabled native unit instead of re-enabling it "through the
backdoor" via a corresponding enabled sysv init script.
Thanks for considering,
Ma
17 matches
Mail list logo
