On Mon, Aug 08, 2005 at 02:19:35PM -0400, Stephen Gran wrote: > This one time, at band camp, Marc Haber said: > > On Mon, Aug 08, 2005 at 09:18:56AM -0400, Stephen Gran wrote: > > > Upstream developed the rough communication protocol (PING, RELOAD, > > > SHUTDOWN, etc), and they prefer to use it over signals. However, for a > > > third party app, I think that using signals is appropriate. I will put > > > a reload-database target in the init script that clamav-data can use. > > > Does that sound OK? > > > > Yes, it is perfect for me. Thanks! Will the init script be smart > > enough so that I only need a > > > > if [ -x /etc/init.d/clamav-daemon ]; then > > /etc/init.d/clamav-daemon reload-database > > fi > > > > in my postinst? > > It will be start-stop-daemon, so it should do The Right Thing(TM). I > will test before uploading to make sure, though.
I'd like to adapt clamav-data soon. Can we settle on "reload-database" as target name, and a non-1 exit code if the reload-database call went wrong? Background: I want clamav-data to work with sarge and volatile clamav as well, and thus I need to ignore the 1 exit code that is returned if clamav-daemon reload-databases is executed with an init script that doesn't know the option yet. But I would like to be able to catch errors nevertheless. Greetings Marc -- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things." Winona Ryder | Fon: *49 621 72739834 Nordisch by Nature | How to make an American Quilt | Fax: *49 621 72739835 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
