On Mon, 08 Jan 2024 at 20:42:54 +0300, Vladimir Kudrya wrote:
> On 08/01/2024 19.21, Mantas Mikulėnas wrote:
> > The traditional dbus-daemon keeps a separate environment for services it
> > spawns directly [...], though that it doesn't apply to services it runs
> > via systemd so you need to keep b
So I'm seeing an artifact of dbus-broker.
Is it possible to unset a variable from native dbus execution environment?
On 08/01/2024 19.21, Mantas Mikulėnas wrote:
The traditional dbus-daemon keeps a separate environment for services
it spawns directly (i.e. those that don't specify SystemdServic
On Mon, 8 Jan 2024 at 11:49, port19 wrote:
> Hi all,
>
> we currently have a monitoring check that alerts us of a service-specific
> config file having changed more recently than the services last restart.
> We retrieve the restart time via `systemctl show
> --property=ActiveEnterTimestamp`.
> I
The traditional dbus-daemon keeps a separate environment for services it
spawns directly (i.e. those that don't specify SystemdService= in their
D-Bus .service files), though that it doesn't apply to services it runs via
systemd so you need to keep both in sync.
On the other hand, dbus-broker runs
Hello.
In context of a modern systemd-managed user session, is there a separate
dbus activation environment, or is it merged with systemd? If one
intends to manage environment variables, is systemctl (or
org.freedesktop.systemd1.Manager Environment) enough?
A variable added by dbus-update-ac
Hi, thank you for the answer.
I use the linux-generic partition to put raw images as the [Source] for
systemd-sysupdate. For now, I don't want to spawn a http server for this.
So you mean I need to have this kind of partition table?
+-+--+++---
You shouldn't be using a linux-generic partition for updates. You need (at
least) two of the same kind of partition to switch between whenever there's
an update
On Mon, Jan 8, 2024, 06:46 Renjaya Raga Zenta wrote:
> Hi,
>
> I've been experimenting with systemd-sysupdate, trying to understand how
Hi all,
we currently have a monitoring check that alerts us of a service-specific
config file having changed more recently than the services last restart.
We retrieve the restart time via `systemctl show
--property=ActiveEnterTimestamp`.
Is there a comparably elegant way to retreive the reload
Hi,
I've been experimenting with systemd-sysupdate, trying to understand how it
works.
I created a Fedora 39 image¹ with mkosi from the GitHub repo. It has 3
partitions:
1) esp
2) root
3) linux-generic (to put updates)
The root and third partition will be expanded on firstboot via
systemd-growfs
