From: Joshua J. E. <jj...@sa...> - 2002-11-01 00:08:04
|
I think I'm getting very close now. I'm finally catching some RARPs with beoserv when a slave boots, although the slave dies pretty quickly. The last thing seen on the slave is: boot: Server IP address: 10.0.4.100 boot: My IP address : 10.0.4.10 boot: starting bpslave: bpslave -d -i 10.0.4.100 2223 bpslave: IO daemon started; pid=11 beoserv on the master shows: beoserv: RARP: 00:30:59:00:98:26 == 10.0.4.10 beoserv: Starting node_up worker for 1 clients. nodeup : Child process for node 0 died with signal 4 I'm booting from an elf image created from a standard bproc kernel, along with the initrd created by 'beoboot -2'. Is this considered a badbadthing? Do I need to roll my own initrd and run 'bpslave' from it? Also, what is the role of the 'bootfile' parameter in /etc/beowulf/config? It looks like beoserv feeds it to a slave after a RARP request, but changing it seems to have no effect. Sorry for the onslaught of questions, free beer at SC for all who help. :) -JE ----------------------------------------------- Josh England Sandia National Laboratory, Livermore, CA Distributed Information Systems email: jj...@sa... phone: (925) 294-2076 |