1. 21 Mar, 2000 1 commit
  2. 20 Mar, 2000 4 commits
  3. 19 Mar, 2000 2 commits
  4. 13 Mar, 2000 2 commits
  5. 12 Mar, 2000 12 commits
  6. 10 Mar, 2000 1 commit
  7. 09 Mar, 2000 6 commits
  8. 08 Mar, 2000 1 commit
  9. 07 Mar, 2000 6 commits
    • Martin Mareš's avatar
      839380d7
    • Martin Mareš's avatar
      f30b86f9
    • Martin Mareš's avatar
      3eb0b586
    • Martin Mareš's avatar
    • Martin Mareš's avatar
      Added protocol debugging flags (protocol.h: D_xxx), parsing of them · 96d8e3bf
      Martin Mareš authored
      in configuration files and commands for manipulating them.
      
      Current debug message policy:
      
         o  D_STATES, D_ROUTES and D_FILTERS are handled in generic code.
         o  Other debug flags should be handled in the protocols and whenever
            the flag is set, the corresponding messages should be printed
            using calls to log(L_TRACE, ...), each message prefixed with
            the name of the protocol instance. These messages should cover
            the whole normal operation of the protocol and should be useful
            for an administrator trying to understand what does the protocol
            behave on his network or who is attempting to diagnose network
            problems. If your messages don't fit to the categories I've defined,
            feel free to add your own ones (by adding them to protocol.h
            and on two places in nest/config.Y), but please try to keep the
            categories as general as possible (i.e., not tied to your protocol).
         o  Internal debug messages not interesting even to an experienced
            user should be printed by calling DBG() which is either void or
            a call to debug() depending on setting of the LOCAL_DEBUG symbol
            at the top of your source.
         o  Dump functions (proto->dump etc.) should call debug() to print
            their messages.
         o  If you are doing any internal consistency checks, use ASSERT
            or bug().
         o  Nobody shall ever call printf() or any other stdio functions.
      
      Also please try to log any protocol errors you encounter and tag them
      with the appropriate message category (usually L_REMOTE or L_AUTH). Always
      carefully check contents of any message field you receive and verify all
      IP addresses you work with (by calling ipa_classify() or by using the
      neighbour cache if you want to check direct connectedness as well).
      96d8e3bf
    • Martin Mareš's avatar
      Renamed command `shutdown' to `down', so that `s' can be used as an · c801e1fb
      Martin Mareš authored
      abbreviation for `show'.
      c801e1fb
  10. 05 Mar, 2000 1 commit
  11. 04 Mar, 2000 4 commits