| … | |
… | |
| 252 | later we will see how we can do all this without even passing anything to |
252 | later we will see how we can do all this without even passing anything to |
| 253 | C<configure>! |
253 | C<configure>! |
| 254 | |
254 | |
| 255 | Back to the function call in the program: the first parameter, C<nodeid>, |
255 | Back to the function call in the program: the first parameter, C<nodeid>, |
| 256 | specified the node ID (in this case C<eg_receiver/%u> - the default is to |
256 | specified the node ID (in this case C<eg_receiver/%u> - the default is to |
| 257 | use the node name of the current host plus C</%u>, which goves the node a |
257 | use the node name of the current host plus C</%u>, which gives the node a |
| 258 | name with a random suffix to make it unique, but for this example we want |
258 | name with a random suffix to make it unique, but for this example we want |
| 259 | the node to have a bit more personality, and name it C<eg_receiver> with a |
259 | the node to have a bit more personality, and name it C<eg_receiver> with a |
| 260 | random suffix. |
260 | random suffix. |
| 261 | |
261 | |
| 262 | Why the random suffix? Node IDs need to be unique within the network and |
262 | Why the random suffix? Node IDs need to be unique within the network and |
