Hi,

I would recommend that you go for a systemd drop-in file [1].
That would be something like a small snippet placed to /etc/systemd/system/avahi-daemon.service.d/override.conf

In that file place something like
[Service]
ExecStart=
ExecStart=<new command line with your custom options>

this way you don't need to alter the upstream recipe with weird sed hacks or similar.

This drop-in file could be packaged by any recipe or bbappend.

[1] https://coreos.com/os/docs/latest/using-systemd-drop-in-units.html

On 14.11.20 17:28, Howard wrote:
Hi:

I've been digging through meta/recipes-connectivity trying to figure out how I can override the avahi-daemon startup parameters.   However I am not finding where the avahi-daemon.service file gets created, or if there is a way to pass in different parameters so that it gets created with my startup parameters.

I need to start the daemon with the --no-chroot option in order for it to see a symlink to a file  /etc/avahi/services/MyAvahiService.service in a writeable partition.

Is there a clean way to do this or do I have to do the brute-force method of either killing it at runtime and restarting w/ --no-chroot, or doing a postinst step and paving over the original avahi-daemon.service file with my own?

Thanks

Howard





-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#51380): https://lists.yoctoproject.org/g/yocto/message/51380
Mute This Topic: https://lists.yoctoproject.org/mt/78253462/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to