Jon,
Here you have some docs on the epmd: http://erlang.org/doc/man/epmd.html
-Alvaro
On Dec 1, 2010, at 2:02 PM, Ulf Wiger wrote:
> Actually, in general, you _should_ leave it running, as other applications on
> your system may depend on it.
>
> BR,
> Ulf W
>
> Ulf Wiger
> CTO, Erlang Solut
Actually, in general, you _should_ leave it running, as other applications on
your system may depend on it.
BR,
Ulf W
Ulf Wiger
CTO, Erlang Solutions, Ltd
http://www.erlang-solutions.com
Justin Sheehy skrev:
>Jon,
>
>You can just leave empd running. That is standard erlang runtime
>behavior
Jon,
You can just leave empd running. That is standard erlang runtime
behavior and generally won't cause any problems.
-Justin
On Tue, Nov 30, 2010 at 9:59 AM, Jon Brisbin wrote:
> I'm running the pre-built binaries for Riak 0.13 (and 0.12 x64, for that
> matter) for OS X 10.6.
> When I do a
Setting up my Rails app to run it's tests has been up to this point a
matter of having a config/ripple.yml file like the following:
development:
port: 8091
host: localhost
test:
port: 8098
host: localhost
Then making sure Riak is running with:
`$RIAK_HOME/rel/riak/bin/riak start`
I'm w
I'm still struggling with some unexpected results in running tests for the Java
support I'm writing for Grails and Spring Data.
As an example, I ran the full Gorm TCK test suite against my local Riak server
(0.13.0) and had 3 failures out of 103. Not bad, though my goal is 0 failures
in 103 tes
Things should be fine if you choose to kill it or not, epmd will start as
needed and there isn't a difference in between the versions shipped with 0.13.x
or 0.12.x.
Grant Schofield
Developer Advocate
Basho Technologies.
On Nov 30, 2010, at 8:59 AM, Jon Brisbin wrote:
> I'm running the pre-bu
I'm running the pre-built binaries for Riak 0.13 (and 0.12 x64, for that
matter) for OS X 10.6.
When I do a "riak stop", there is one process still running. The epmd -daemon
process. I have to kill it manually.
In my testing, I'm starting 0.13, running a test, then shutting it down,
starting 0
Looking at the next release that's ~3 weeks away, I don't think this
fix will make it in, sorry. :( It's always a balancing act with bugs
and features...
D.
On Tue, Nov 30, 2010 at 1:30 AM, francisco treacy
wrote:
> I'm running into this issue often... Does Target Milestone: 'Dakota'
> mean thi
I'm running into this issue often... Does Target Milestone: 'Dakota'
mean this bugfix could make it into 0.14?
Thanks,
Francisco
2010/11/19 Dan Reverri :
> Hi Francisco,
> This is a known issue:
> https://issues.basho.com/show_bug.cgi?id=800
> Thanks,
> Dan
> Daniel Reverri
> Developer Advocate
