likwid-accessD fails silently on Phi

[GoogleCodeExporter]

What steps will reproduce the problem?
1. hack your Makefile to build likwid-accessD with ICC for Phi
2. run likwid-accessD on the coprocessor

What is the expected output? What do you see instead?

There is no output. The daemon fails to start. It attempts to write the 
following message to syslog, but fails because syslogd isn't running:

> ERROR - [src/access-daemon/accessDaemon.c:514] - Unsupported processor. 
Exiting!

What version of the product are you using?

3.1.0

Please provide any additional information below.

likwid-accessD should check the processor family before it forks the daemon 
process. Then it can report failure synchronously and the caller (e.g. 
likwid-perfctr) will know that it failed.

Original issue reported on code.google.com by pe...@quux.net on 7 Feb 2014 at 9:18

[GoogleCodeExporter]

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

• Changed state: Accepted

[GoogleCodeExporter]

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

[GoogleCodeExporter]

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

[GoogleCodeExporter]

Original comment by jan.trei...@gmail.com on 12 Feb 2014 at 3:17

• Changed state: Fixed