2 - multiline log entries in gcm_input.
3 - several files don't have version identifiers; a simple $Id in the
4 comment would help in finding packaging bugs. (Also recommended for
5 the documentation files)
6 - Some files have lines longer that 80 characters.
7 - Most makefiles and stylesheets miss a copyright header.
8 - There is no reference to the gnucomo website.
9 - There is no list of required and recommended software.
10 - A step-by-step installation guide is missing.
11 - The installation description in the manifest must be
12 updated to include the ./configure script.
13 - The input filename for gcm_input can be a command argument.
14 - When gcm_input can not make a connection to the database, its input
15 message will be lost. In such a case, gcm_input should store the
16 message in a spool directory for a retry later on.
19 - Too many loglines, notifications, parameters are shown on one page
20 - When all the notifications of an object are shown for each notification
21 shown it has to be registered who was looking at it (just as looking at
22 the detailed notification).
23 - A page with notification (independent of object) (with sort capabilities
24 and grouping per urgency).
25 - A page with detailed object-data
26 - With an object one should be able to indicate what OS is being used
27 - Webpages should look more 'sexy'
31 - When looking at a logline it is usefull to see the related log_adv records
32 - Linking database users to objects (only certain objects can be shown to certain users)
35 - Indicate to gcm_input what type of data is delivered
36 - Update statistics in the object table when a new parameter is entered
37 - Update statistics in the object table when a new notification is entered
41 - Create indexes on log_adv_daemon_email
42 - Build IP-database on the basis of whois
43 - Work on undetected kernellines
44 - Create mechanism for starting and ending the daemon.
45 - Performance check on the gnucomo-database