Hello Damien,
> I would prefer if mcollective.xml is fixed to use a full path to data
> directory.
> For example, you could use something like :
> ${activemq.base}/data
>
> (where activemq.base property will automatically be set to
> /var/lib/activemq/[instance]/)
you are right - my configuration is wrong. I have fixed that - so my
patch is not needed.
> > But I found an other problem, when I try to start the ActiveMQ
> > Instance onboot:
> >
> > root@sid:~# update-rc.d activemq-mcollective defaults
> > update-rc.d activemq-mcollective defaults
> > update-rc.d: using dependency based boot sequencing
> > insserv: script activemq-mcollective: service activemq already
> > provided! insserv: exiting now!
> > update-rc.d: error: insserv rejected the script header
>
> Hum, nice spot.
> I don't think my first approach will work nicely : we can't split each
> instance in its own init.d script.
> I'll work on something similar that postgresql (one main script to
> start everything)
yep your are right.
Thanks again for your great work on ActiveMQ!
Greets,
Jonas
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
