I just rebuilt syslog-ng against libol-0.2.17 to be sure of the libol version. I went ahead and removed the cron job that restarts syslog-ng, and I'll see if this error keeps happening. -- Nate On Sun, 18 Jun 2000, Balazs Scheidler wrote: > > hmmm... that seems to be a problem in libol, can you send me your libol > version?