Job objects encapsulate scheduled or running jobs. Each unit can
have none or one jobs in the execution queue. Each job is
attached to exactly one unit.
node /org/freedesktop/systemd1/job/666 {
interface org.freedesktop.systemd1.Job {
methods:
Cancel();
GetAfter(out a(usssoo) jobs);
GetBefore(out a(usssoo) jobs);
properties:
@org.freedesktop.DBus.Property.EmitsChangedSignal("const")
readonly u Id = ...;
@org.freedesktop.DBus.Property.EmitsChangedSignal("const")
readonly (so) Unit = ...;
@org.freedesktop.DBus.Property.EmitsChangedSignal("const")
readonly s JobType = '...';
readonly s State = '...';
};
interface org.freedesktop.DBus.Peer { ... };
interface org.freedesktop.DBus.Introspectable { ... };
interface org.freedesktop.DBus.Properties { ... };
};
Methods
Cancel() cancels the job. Note that this will remove a job from
the queue if it is not yet executed but generally will not cause
a job that is already in the process of being executed to be
aborted. This operation may also be requested via the CancelJob()
method of the Manager object (see above), which is sometimes
useful to reduce roundtrips.
Properties
Id is the numeric Id of the job. During the runtime of a systemd
instance each numeric ID is only assigned once.
Unit refers to the unit this job belongs to. It is a structure
consisting of the name of the unit and a bus path to the unit's
object.
JobType refers to the job's type and is one of "start",
"verify-active", "stop", "reload", "restart", "try-restart", or
"reload-or-start". Note that later versions might define
additional values.
State refers to the job's state and is one of "waiting" and
"running". The former indicates that a job is currently queued
but has not begun to execute yet. The latter indicates that a job
is currently being executed.
