make rc script work on other systems too

make rc script work on debian, ubuntu and sles too

Signed-off-by: Sven Nierlein <sven@consol.de>
clean some more files

clean files which are not part of the repository.

Signed-off-by: Sven Nierlein <sven@consol.de>
naemon/Makefile.am: Add wpres-phash.h to CLEANFILES

Signed-off-by: Adam James <adam.james@transitiv.co.uk>
fix rc script

use start-stop-daemon if available, unfortunatly daemon has different options
and behaviour on various systems.

Signed-off-by: Sven Nierlein <sven@consol.de>
changed version

the first release should not have version 4

Signed-off-by: Sven Nierlein <sven@consol.de>
Move tests out of harms way (=out of the source code dir)

Tests is great, and keep the tests organized in the same way as the
source is a good thing. But it's much easier to keep the tests in a
separate directory, but keep the structure as the soruce directory,
to see what is tested.

Change-Id: I874c47474a8a8204d0f5eb10cafb8982be330262
Signed-off-by: Max Sikstrom <msikstrom@op5.com>
Worker: break out to a seperate subproject.

Keeping workers and lot of perferical stuff embedded in the code
base, it's much harder to port and change stuff. To be able to
rewrite it to handle multiple configurations at the same time, lot of
stuff needs to be rewritten. That means, it's much easier to keep the
codebase splitted up.

Signed-off-by: Max Sikstrom <msikstrom@op5.com>
Remove include-everything-headers

Include-everything-headers makes it alsmost impossible to track
dependencies, when trying to refactor. It's not that hard when you
develop to actually include the nessecary files when using a new
header. And when including a new header you can actually think about
if it's a good idea to use that header in that particular source
file. That in helps making the code more structured.

There is actually almost nothing good by having those
include-everything-headers.

Change-Id: I8e0e0977bb16fa09c212792c218e6ecf9024a254
Signed-off-by: Max Sikstrom <msikstrom@op5.com>
Add -Werror, warnings is not a good thing to have.

Warnings mostly appears by a reason, and is almost always just easy
to fix. Therefore, treat warnings as errors, so we find all those
"implicit declartation" and dangerous implict typecasts.

Also fix the warnings that appeared

Change-Id: I7012964838c76127d3d45dabc533c344b12f5bd5
Signed-off-by: Max Sikstrom <msikstrom@op5.com>