Am 2025-03-19 19:49, schrieb Gleb Popov:
Hey fellow portophiles.

A lot of ports install rc scripts that are used to start some
service[s] during the system boot process. Programs launched from
within the rc script are expected to daemonize to let the boot
sequence continue. Daemonization can be performed either

- by the application itself using whatever means it has
- or by the porter/rc script writer which usually employs daemon(8) to
do the job

Programs that know how to daemonize themselves often provide a way to
disable this feature, which brings porter to a choice - use an
in-house daemonization functionality or resort to wrapping the program
invocation into daemon(8). I believe it'd be nice to have a paragraph
talking about this topic in Porter Handbook?

I use it in some ports where the application-method was not adequate for some reasons. An example would be devel/sonarqube-community where I have the possibility to specify if it shall restart on exit or not (the application has a "restart" button in the WUI which only works if daemon restarts the app on exit, and the app relies on some supervisor which I replaced with daemon).

I think this is a good idea, if the docs explain when it is a good idea to use daemon and when not.

Bye,
Alexander.

--
http://www.Leidinger.net [email protected]: PGP 0x8F31830F9F2772BF
http://www.FreeBSD.org    [email protected]  : PGP 0x8F31830F9F2772BF

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to