This sort of illustrates a benign version of what I'm talking about. Here the `riak_test` node doesn't have the module so the node which has the first daemon run passes its ebin on it `riak_test` which then passes it on to every other node in the cluster despite them already having the module. Not sure how big of a deal this is since its just extra paths to search when code is loaded. {shrug}

```
12:42:12.014 [info] start_set_net_ticktime_daemon: adding to code path for node 'dev1@127.0.0.1': "/home/jordan/sandbox/basho/rt/riak/current/dev/dev1/lib/riak_core-1.4.2-253-gda2cb42/ebin"
12:42:12.014 [info] start_set_net_ticktime_daemon: adding to code path for node 'dev2@127.0.0.1': "/home/jordan/sandbox/basho/rt/riak/current/dev/dev1/lib/riak_core-1.4.2-253-gda2cb42/ebin"
12:42:12.014 [info] start_set_net_ticktime_daemon: adding to code path for node 'dev3@127.0.0.1': "/home/jordan/sandbox/basho/rt/riak/current/dev/dev1/lib/riak_core-1.4.2-253-gda2cb42/ebin"
12:42:12.014 [info] start_set_net_ticktime_daemon: adding to code path for node 'dev4@127.0.0.1': "/home/jordan/sandbox/basho/rt/riak/current/dev/dev1/lib/riak_core-1.4.2-253-gda2cb42/ebin"
```