[solved] backup didn't shut down kodi

DietPi v10.2.3, arm64, RPi 5 Model B (aarch64)

Fresh install from the current pi5 image, connected to NAS via NFS to create a dietpi-backup for the fresh install, Monitor was still showing kodi while backup was running.

A complain / ERROR that avahi-daemon was not shut down could be seen.

Cancelled the backup, deleted the backup and glanced back to monitor to see kodi down, backup now didn’t complain of course.

Cheers.

At this time, it is not intended that dietpi-backup stops Kodi. Therefore, this is not a bug; it is functioning as designed.

Ok, had faint memory of kodi getting shut down and when i was running backups on last install i didn’t usually run with monitor when doing backups.

The backup only stops known background services. Kodi however is a foreground application.

The Avahi daemon however is a background service that is (attempted to be) stopped.

Kodi is compiled against the libavahi-client library, hence it talks to the Avahi daemon in circumstances, but not sure exactly in which situation of for which features. Theoretically it clould block the graceful stop of the Avahi daemon somehow. But in practice, it talks to it via DBus, and I am not aware that there was any mechanism to prevent the counter side that is talked to via DBus/IPC from being stopped. I’d expect Kodi to just throw errors (on the parent console) when it cannot find the Avahi daemon anymore while trying to talk to it :thinking:.

Could be tested/investigated further, but in general it makes sense to stop applications like Kodi before doing a backup anyway.