On 06/03/2009, at 3:38 AM, Jeffrey Chupp wrote: > Figured out the problem, and it was, predictably, something stupid on > my part. I had a searchd running, so the features tried to use it and > couldn't find anything since it was holding different indices. > Killing that instance allowed the features to run properly.
Ah, good to hear it was something simple :) > Is there a way to either 1) warn when running features if an existing > searchd is running or 2) run the features searchd on a different port? 1) well, on flavours of Unix, should be possible to determine whether a port is in use. So technically, yes. 2) would mean a sphinx.yml file is added to the feature structure - which is viable, but I've kept it to the standard because, well, it is the standard, and we know that port probably isn't going to be used by anything else but Sphinx. I also don't have a habit of leaving apps & Sphinx running for super-long periods of time (but then, the only apps I have running Sphinx are my manual test ones for each Rails version) - so maybe my situation isn't the norm. If there was great demand, I'd consider it, but for now, I think it's fine as it is. -- Pat --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Thinking Sphinx" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/thinking-sphinx?hl=en -~----------~----~----~----~------~----~------~--~---
