Closed GoogleCodeExporter closed 9 years ago
I think the most user friendly way is to give a notice during build and set
everything right in the Makefile overruling settings in config.mk, means
disable accessD and set accessmode to direct.
Original comment by jan.trei...@gmail.com
on 8 Feb 2014 at 1:57
I agree that, for Phi, it would be ideal to not build this at all. However I do
think it would still make more sense for the daemon to perform its checks
before it forks, so that it can report failure to its parent through via an
exit code.
Original comment by pe...@quux.net
on 10 Feb 2014 at 2:38
It is not possible to return a error code because the execve call does not
return on success.
Still I moved the architecture detection before the daemonize and output an
error to stderr if you try to start accessD on an unsupported architecture.
Original comment by jan.trei...@gmail.com
on 12 Feb 2014 at 3:03
Original comment by jan.trei...@gmail.com
on 12 Feb 2014 at 3:17
Original issue reported on code.google.com by
pe...@quux.net
on 7 Feb 2014 at 9:18