RE: configuration patch - final version

[Jan-Henrik Haukeland]

> Sounds good. The BER rules uses the same princip - it defines tag for
> each data type + length + data part length. There's also support for
> structures, etc. (primitive and constructed types, support for
> user-defined data type classes),  is possible to validate the stored
> data in the parser as well. Problem is, that it is little bit more
> complicated.

Yep, we therefore do this post-parse. That is; we let the parser parse the
monitrc file and when the parse is finished we read the state file and update
if necessary state values. (The only value we need to update is do_validate
right?) So in p.y:parse() we simply add (the last lines before END_LOCK:


  /* Creation of the global process list is synchronized  */
  LOCK(Run.mutex)

      initialize();
      yyparse();
      fclose(yyin);

      /* If defined - add the last process to the process list */
      if(current) {

        createprocinfo();
        addprocess(current);

      }

      /* Check the sanity of any dependency graph */
      check_depend();

     /* Check if a state file is present and that the timestamp is not to old
*/
    if(has_statefile()) {

load_and_replace_just_parsed_new_values_with_old_do_validate_values_from_state_
file();
    }

  END_LOCK;


Ps. I'm on my way to Sweden right now to buy some chewing tobacco :-) but I'll
test this when I get back!

Cheers!

Jan-Henrik