On Mi, 13.03.19 11:40, aleivag (alei...@gmail.com) wrote:
> Hi all:
>
> Sorry to bring this up again... here is what i plan to do, i'm just asking
> if this make sense.
>
> (the context is that i start a transient unit, and pass tty fd, and i need
> to know when the unit is dead, so i can close my
On Mo, 18.02.19 16:46, aleivag (alei...@gmail.com) wrote:
> 1.- Is this change in behaviour, intended, or a side effect of something
> else?
When a unit is first created it is in "dead" state. It only changes to
"active" state as soon as it actually starts running.
Note that PropertiesChanged is
Hi all:
Sorry to bring this up again... here is what i plan to do, i'm just asking
if this make sense.
(the context is that i start a transient unit, and pass tty fd, and i need
to know when the unit is dead, so i can close my fds)
`systemd1.Manager.StartTransientUnit` returns a job in the form o
Hi All:
i notice a change of behaviour that broke a couple of my scripts between
v239 and v240, and wanted to know that maybe i was always assuming the
wrong thing, so here it goes:
so i subscribe to
"type='signal',"
"sender='org.freedesktop.systemd1',"
"path=
