Hi Gary, Your answer was needed as well. John is working on the init script that the LOSA should use to deploy the new lp-forking-service server. That requires calling bzr and your answer provides that bit of the response.
The other missing bit is where are the LOSA init script hosted. -- Francis J. Lacoste [email protected] On November 24, 2010, Gary Poster wrote: > On Nov 24, 2010, at 1:13 PM, Francis J. Lacoste wrote: > > On November 24, 2010, Gary Poster wrote: > >> John Arbash Meinel > >> > >>> <[email protected]> wrote: > >>> ... > >>> > >>>> I've posted to the RT request an init script that does the 'less > >>>> tasteful' way. ATM init scripts are not in the launchpad codebase, and > >>>> exist somewhere I'm not quite sure of. > >>> > >>> I don't know either. > >> > >> They are in the eggs themselves. > > > > John was talking about the init scripts used by the LOSA to start/stop > > daemon. > > > > That's managed in bzr branch, that might not even be on Launchpad itself. > > > > A losa will be able to answer that question precisely. > > I was trying to answer John's initial question in this thread: > > """ > As part of the forking service work, I'm trying to put together the init > script. The current blocker is finding the 'bzr' script itself to run. > > As near as I can tell, the path to use is: > $launchpad/eggs/bzr-2.2.1-py2.6-linux-i686.egg/EGG-INFO/scripts/bzr > > > The init script I'm cribbing from is using $launchpad/bin/twistd, but > there isn't a matching $launchpad/bin/bzr. > """ > > That's what the branch I gave does. That said, maybe I still misunderstand > something. > > Gary
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
