On Tue, Feb 17, 2009 at 02:12:20PM +0100, Andreas Metzler wrote:
> On 2009-02-17 "Eugene B. Berdnikov" <b...@protva.ru> wrote:
[...]
> > if [ "${QUEUERUNNER}" != "no" ] ; then
> > -# Flush exim queue
> > - /usr/sbin/exim4 -qqf ${QUEUERUNNEROPTIONS} ${COMMONOPTIONS}
> > +# Start queue runner in backgroud
> > + (
> > + /usr/sbin/exim4 -qqff ${QUEUERUNNEROPTIONS} ${COMMONOPTIONS} \
> > + < /dev/null > /dev/null 2>&1 &
> > + )
> > fi
> Is there a policy on ip-up/down?
I can't find anything. Let's use common sense.
> Should this stuff be done in the
> background, or should we be able to rely on the fact that after ip-up
> has finished all started jobs are done?
Up/down scripts may be of several kinds, at least two:
1. interface configuration tasks,
2. some triggers for jobs.
I belive that queue running has no relation to iface configuration
and should be done in background. In some situations (as in my case),
queue run may be meaningless if configuraion is not completed.
> I disagree about unfreezing mails automatically, BTW. They are usually
> frozen for a reason and thawing often results in new freeze again.
Freezing may be caused by the DNS failure or some other result of
network inaccessibility. It's good if such mail takes chance to be
delivered, and IMHO there is no more trouble if some broken mail
became frozen again.
--
Eugene Berdnikov
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
