search for: pt2pt

Guys, I'm having troubles with Rmpi on Linux. I got it to work on windows, but on Linux (SuSE 64 bit), using OpenMPI, I can't seem to get it to work :( When I do library(Rmpi) I get the warning: mca: base: component_find: unable to open osc pt2pt: file not found (ignored) Interestingly enough all the examples from the snow tutorial ( http://www.sfu.ca/~sblay/R/snow.html) work despite the warning. But then, when I run my app I get mca: base: component_find: unable to open osc pt2pt: file not found (ignored) mca: base: component_find: unab...

...CentOS per se.? I have 2 servers that are on two networks.? I did NOT set this up.? The NIC went bad and it has been replaced.? I knew enough to update the HW address in the ifcfg-* files.? The network service restarts successfully without errors.? However I cannot connect via ping or ssh with the pt2pt network setup on 192.168.x.*.? When I use our internal network ip addresses it is fine. I am not sure how to troubleshoot this separate connection.?? What can I provide here that will allow someone to help?? Thanks in advance.? I tried searching a bit but didn't find anything of use so far. KM

...trying to get openmpi, Rmpi and SNOW running on a Myrinet/GM cluster. I'm not an IT expert, but I surely could use a working installation of Rmpi and SNOW. I try to load the Rmpi library and get the following: > library(Rmpi) [master:07230] mca: base: component_find: unable to open osc pt2pt: file not found (ignored) -------------------------------------------------------------------------- [0,0,0]: Myrinet/GM on host master was unable to find any NICs. Another transport will be used instead, although this may result in lower performance. Then if I start a cluster, only nodes on Mast...

...ntOS] A question on networking (CentOS 6) On 02/13/2017 06:55 AM, KM wrote: > The NIC went bad and it has been replaced.? I knew enough to update the HW address in the ifcfg-* files.? The network service restarts successfully without errors.? However I cannot connect via ping or ssh with the pt2pt network setup on 192.168.x.*.? When I use our internal network ip addresses it is fine. That's not much to go on.? The output of "ip addr show" and "ip route show" might help you figure out what's going on.? Do your interfaces have the expected names?? Do they have th...

On 02/13/2017 06:55 AM, KM wrote: > The NIC went bad and it has been replaced. I knew enough to update the HW address in the ifcfg-* files. The network service restarts successfully without errors. However I cannot connect via ping or ssh with the pt2pt network setup on 192.168.x.*. When I use our internal network ip addresses it is fine. That's not much to go on. The output of "ip addr show" and "ip route show" might help you figure out what's going on. Do your interfaces have the expected names? Do they have th...

...entOS] A question on networking (CentOS 6) On 02/13/2017 06:55 AM, KM wrote: > The NIC went bad and it has been replaced.? I knew enough to update the HW address in the ifcfg-* files.? The network service restarts successfully without errors.? However I cannot connect via ping or ssh with the pt2pt network setup on 192.168.x.*.? When I use our internal network ip addresses it is fine. That's not much to go on.? The output of "ip addr show" and "ip route show" might help you figure out what's going on.? Do your interfaces have the expected names?? Do they have th...

Hi. I experimented a bit with collecting entropy from the time it takes for device_attach() to run (in CPU cycles). It seems that those times have enough variation that we can use it for entropy harvesting. It happens even before root is mounted, so pretty early. On the machine I'm testing it, which has minimal kernel plus NIC driver I see 75 device_attach() calls. I'm being very careful