Steffen Nurpmeso:
> Wietse Venema wrote in
> <4bcgr00pr0zj...@spike.porcupine.org>:
> |Steffen Nurpmeso:
> |> It would be great if a hook could be called for such events. Even
> |> a simple fork+detach+exec+forget approach would be really great,
> |> with an event indicator and an IP address as an argument.
> |
> |We don't do ad-hoc special-case solutions.
>
> Yes. That is good. But, on the other hand, trying to create
> a very generic interface can become an endless undertaking.
No, it doesn't. But, as this thread has already demonstrated, doing
a proper job does take more thought than a quick fix. Fred Brooks
estimated the cost difference between an ad-hoc program versus
code that is part of at maintainable system.
In this case, it would require a logging API that takes a 'server
state' argument, plus a callback function that serializes that server
state as name-value pairs along with the error messge. It should
probable be JSON format, but other loss-free formats would work, too.
Wietse
