small addendum: in my initial research, i left out the topic of
avahi-publish, which is a process that does nothing but publish a
service.

while avahi-publish could both be used by the daemons themselves and
init scripts, i'd like to keep the proposal upright. adding and removing
a file to/from a directory is easier to handle in an init script that
keeping a second process alive, which involves starting
start-stop-daemon another time, keeping track of another pid file, and
last but not least having another process linger around -- avahi-daemon
can already do what the avahi-publish process would do with less
overhead.

for sake of completeness, here's what i should have written about
avahi-publish in the "existing solutions" section:

* using avahi-publish

  a relatively simple option, which only requires the daemon to launch a
  sub-process and handle it until shutdown.

before "well, so a simple solution for daemons to announce sth already
exists", please keep in mind that even if it's relatively simple,
announcing services without upstream support would still mean a patch to
the daemon in question, as opposed to two lines in the init script.

Attachment: signature.asc
Description: Digital signature

Reply via email to