From owner-freebsd-ports@FreeBSD.ORG  Thu Mar 18 22:38:50 2004
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id F3A4016A4CE
	for <freebsd-ports@freebsd.org>; Thu, 18 Mar 2004 22:38:49 -0800 (PST)
Received: from mail.visp.ru (srv1.visp.ru [213.154.182.2])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 61C4143D1F
	for <freebsd-ports@freebsd.org>; Thu, 18 Mar 2004 22:38:49 -0800 (PST)
	(envelope-from alexz@visp.ru)
Received: from alex by mail.visp.ru with local (Exim 4.30; FreeBSD)
	id 1B4DeZ-00093z-EK
	for freebsd-ports@freebsd.org; Fri, 19 Mar 2004 09:38:47 +0300
Date: Fri, 19 Mar 2004 09:38:47 +0300
From: Alexander Zagrebin <alexz@visp.ru>
To: freebsd-ports@freebsd.org
Message-ID: <20040319063847.GA34186@srv1.visp.ru>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.6i
Subject: clamd 0.67.1 doesn't reopens log file
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Mar 2004 06:38:50 -0000

I have troubles with clamd's log rotation.
The problem in that, clamd doesn't reopens log file after signal.
To repeat:
  cd /var/log/clamav
  mv clamd.log clamd.log.1
  kill -1 `cat /var/run/clamav/clamd.pid`
After this clamd writes to log
  Fri Mar 19 09:21:59 2004 -> SIGHUP catched: log file re-opened.
but doesn't creates clamd.log and continues write to clamd.log.1

Any suggestions (except clamd restarting)?

-- 
Alexander Zagrebin