[Pkg-clamav-devel] [Pkg-clamav-commits] [SCM] Debian repository for ClamAV branch, debian/unstable, updated. debian/0.94.dfsg.1-1-3-g2b91058

[Michael Tautschnig]

> This one time, at band camp, Michael Tautschnig said:
> > > Doesn't this just mean that if the milter is configured first, it will
> > > wait and then fail, instead of failing immediately?
> > > 
> > 
> > Omg, of course. But it should be fine if we send the clamav-milter stuff to the
> > background, right? Or is there something that stops us from doing so?
> 
> Aside from the asynchronous feedback to the person watching the display:
> 
> starting clamav-milter ..
> starting clamav-daemon [ok] [ok]
> ...
> 
> and the ick factor :)
> 

Well, yes, that's not really user-friendly. What about the following:

- touch lock-file in clamav-daemon.prerm/upgrade
- check for lock-file in clamav-milter.init/start and create a
  clamav-milter-restart-me, but don't start
- in clamav-daemon.postinst, after starting clamd, check for
  clamav-milter-restart-me and start clamav-milter

I'll try to implement that, but maybe I'm once again missing something.

Best,
Michael

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 194 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/pkg-clamav-devel/attachments/20081123/1cfaa743/attachment.pgp