If I try to compile ZOO with MapServer? 6.2 I obtain this error

/usr/bin/ld: cannot find -lmapserver
collect2: error: ld returned 1 exit status
make: *** [zoo_loader.cgi] Error 1

Hi,

We used zooproject in a clustered mode. So we have a database backend to share ongoing informations of running services between 2 ZOO-Kernel instances. When the load on the cluster increases, some requests fails due to databases errors :

ERROR 1: ERROR: duplicate key value violates unique constraint "services_osid_key" DÉTAIL : Key (osid)=(1593003150) already exists. ERROR 1: ERROR: insert or update on table "responses" violates foreign key constraint "responses_uuid_fkey" DÉTAIL : Key (uuid)=(519e1ea2-b481-11ea-917c-005056b8dc20) is not present in table "services".

• The osid value calculated by the kernel is not unique

The osid is calculated by the script zoo-project/zoo-kernel/zoo_service_loader.c (line 830) : sprintf (tmpBuff, "%i", (cpid + ((int) tp.tv_sec + (int) tp.tv_usec)));

• In some cases, the PID variation is cancelled by the timestamp variation

I know that the current release is a proof of concept, so this request is related to the next release, but attached to the current.

While working on GIS GRASS ZOO integration, i faced several issues and obstacles using the zoo-kernel.

• Parsing wrong commands from command line, or config files with incorrect content, as well as wrong python function bindings resulting in segfaults, which is a kind of frustrating finding errors while attaching new services.
• There are inconsistencies between the command line interface and the cgi interface for Python services (different number of function arguments -> map, input and output vs. input, output)
• Massive use of sprintf and strcmp instead of the more secure versions snprintf and strncmp
• No check of correct memory allocation
• Missing error messages in case something goes wrong with command line parsing, config file parsing and Python function bindings
• Mixing C and C++ code (malloc and new operator used in one file)
• The code need to be re-fractured to split huge functions into smaller parts to reduce redundancy and enhance the stability and maintainability
• Better indention for better readability and maintainability
• more issues will be added as new tickets

Hence i have modified several files in zoo-kernel because of security and stability reasons and added additionally debug output. The modification are made in the kernel and the python loader part.

• Most of the memory allocation is now checked and warnings are printed if memory allocation fails
• I have replaced sprintf with snprintf when possible
• I have replaced strcmp with strncmp when possible
• IMHO wrong memory allocation was fixed
• Indention style for zoo_loader.c changed for better readability (using indent on Linux)

I may have implemented new bugs while trying to reduce them. :/ So intensive testing is needed.

Patch is attached.