Email notification daemons

[Russel Winder]

Vincent,

Thanks for chipping in on this issue.  It turns out that cron is not the
culprit for the problem that is vexing me.  It seems that the Bazaar
hookless email program now (in Karmic) fails to go into daemon mode.
i.e. the -d option fails to do anything now where it used to work fine.

I have raised a bug report:
https://bugs.launchpad.net/bzr-hookless-email/+bug/511815 to cover this.

It seems I had been using an old version of this as I was tracking bzr
+ssh://bazaar.launchpad.net/~bzr/bzr-hookless-email/trunk/ which used to
be lp:bzr-hookless-email but now that reference is to bzr
+ssh://bazaar.launchpad.net/~bzr/bzr-hookless-email/trunk-2a/ --
somewhere along the line the branch got changed and of course Launchpad
is useless as informing people of these sort of changes :-(

Of course if Bazaar stored the lp:... address instead of the expanded
one this wouldn't be a problem.  I have raised bug report
https://bugs.launchpad.net/bzr/+bug/511817

However even with the three extra revisions from the new trunk-2a
instead of trunk version it still fails to go into daemon mode for me.

I guess I will have to look at the source code . . . unless I can
convince Wouter that this is a blocking bug -- which it is -- and that
someone who already knows the code could take a look at the problem, and
if not fix it, give me guidance as to what experiments to do so that I
may provide a fix.



On Sat, 2010-01-23 at 10:21 +0100, Vincent Ladeuil wrote:
> >>>>> "Russel" == Russel Winder <russel.winder at concertant.com> writes:
> 
>     Russel> I used to start Bazaar branch email notification
>     Russel> daemons using @reboot in crontab entries
>     Russel> (cf. lp:bzr-hookless-email).  It seems that Ubuntu --
>     Russel> in its infinite wisdom -- has decided to organize
>     Russel> things so that @reboot entries in crontab entries now
>     Russel> do nothing -- clearly a Karmic thing :-(
> 
> I use @reboot too and also experienced... spurious problems. I
> haven't diagnosed them precisely for Karmic as they occur in a
> context where it's simpler for me to just reboot again.
> 
> My understanding so far is that Karmic is now using upstart to
> speed up the boot significantly. To do that, the underlying model
> has been changed to allow more parallelism (I don't know the
> exact details, just that init tasks have dependencies and they
> run only when their dependencies are satisfied as opposed to the
> previous model where all tasks were serialized). There are
> obviously some bugs there and they seem to be fixed as they are
> discovered.
> 
> To come back to your problem, I suspect that it's not that
> 'crontab entries now do nothing' but instead 'crontab entries try
> to run before their dependencies are satisfied'. That could range
> from 'network enabled' to 'volumes mounted' or what not.
> 
> I worked around a similar issue on OSX by adding a
> 'sleep <as-long-as-needed>' before starting my cron job. 
> 
> Crude and ugly but effective :)
> 
> Hth,
> 
>         Vincent


-- 
Russel.
=============================================================================
Dr Russel Winder      Partner
                                            xmpp: russel at russel.org.uk
Concertant LLP        t: +44 20 7585 2200, +44 20 7193 9203
41 Buckmaster Road,   f: +44 8700 516 084   voip: sip:russel.winder at ekiga.net
London SW11 1EN, UK   m: +44 7770 465 077   skype: russel_winder
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20100124/c665072f/attachment.pgp