On 28-ago-09, at 21:21, pub crawler wrote: > We have the need to run a second instance of Cherokee on a single > server. So two Cherokee servers on same server - one on port 80 and > another on port 82. > > I run cherokee-admin from command line like this: > cherokee-admin -u -b -p 9092 -C > /etc/cherokee/cherokee.conf.images.pubcrawler.com > > Now this configuration file I am editing has port defined as 82 for > Cherokee to listen on. > > I make my changes in the admin - make sure they are saved then proceed > to stop Cherokee from within the admin and the restart it. > > What happens is Cherokee stops the other instance of Cherokee running > on port 80. Starting it, restarts the port 80 instance - which is the > wrong one. > > Am I missing something here? Shouldn't cherokee-admin start/stop the > Cherokee instance related to the config file? Or is that a request for > new feature?
You'll have to configure a different PID file in the second server. In cherokee-admin: Advanced -> Special Files -> PID File That should be enough :) -- Octality http://www.octality.com/ _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
