acassis commented on code in PR #16542: URL: https://github.com/apache/nuttx/pull/16542#discussion_r2152846881
########## Documentation/applications/system/syslogd/index.rst: ########## @@ -27,9 +27,9 @@ not receive or forward logs. .. warning:: - The daemon is currently runs itself in the background using ``fork()``. On - architectures where ``fork()`` is not implemented, the daemon must be - "backgrounded" by using the trailing ``&`` in NSH at the moment. It is also - possible to us ``posix_spawn()`` from a parent program. + The daemon runs itself in the background using ``posix_spawn()`` due to + limitations with the NuttX implementation of ``fork()`` being architecture + dependent. This results in more consistent behaviour, but requires + ``CONFIG_LIBC_EXECFUNCS`` to be enabled. Review Comment: @linguini1 maybe it makes sense to include CONFIG_LIBC_EXECFUNCS as dependence for SYSLOGD. Although the users could run the syslogd in background, running as a daemon is better. I think apps/examples/alarm/alarm_main.c doesn't depends on CONFIG_LIBC_EXECFUNCS and it works like a daemon. Is it possible to use the same strategy? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@nuttx.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
