uff, I am ashamed....

Tracing the problem I found out that the invalid startup packets were not
triggered by the webserver either... looking more precisely I found out
that the messages appeared regularly every 180 seconds in /var/log/messages

This led me to the thought, that this has got to be the monitoring software
which checks if the daemon is still there on a regular basis.

Oh, what stupid I am !

PS. An ip-address in the log-file would have helped me - maybe this could be
added
in a future release?

Sorry, if I bothered you - thanks for your help anyway

Mit freundlichem Gruï¿½

Henrik Steffen
Geschï¿½ftsfï¿½hrer

top concepts Internetmarketing GmbH
Am Steinkamp 7 - D-21684 Stade - Germany
--------------------------------------------------------
http://www.topconcepts.com          Tel. +49 4141 991230
mail: steffen@topconcepts.com       Fax. +49 4141 991233
--------------------------------------------------------
24h-Support Hotline:  +49 1908 34697 (EUR 1.86/Min,topc)
--------------------------------------------------------
System-Partner gesucht: http://www.franchise.city-map.de
--------------------------------------------------------
Handelsregister: AG Stade HRB 5811 - UstId: DE 213645563
--------------------------------------------------------



Tue, 28 May 2002 09:53:58 +0200
"Henrik Steffen" <steffen@city-map.de>
Invalid length of startup packet - solved!