2.5.67-mm3 report
After working around the video symbols compile issue, 2.5.67-mm3 seems to be mostly happy here -
There's an interesting new buglet in 2.5.67-mm3, which I see on both boxes here which have booted 2.5.67-mm3 - I don't see this in -mm2.
The symptom here is that running the "ruptime" command on an -mm3 box shows all hosts down -
Interestingly, the other hosts are getting the rwho broadcasts from the -mm3 box, but the -mm3 box is unable to process rwho broadcasts, including it's own -
Cheers,
Joe
Quoted 7 lines · jjs
After working around the video symbols compile issue, 2.5.67-mm3 seems to be mostly happy here -
There's an interesting new buglet in 2.5.67-mm3, which I see on both boxes here which have booted 2.5.67-mm3 - I don't see this in -mm2.
Quoted 6 lines
The symptom here is that running the "ruptime" command on an -mm3 box shows all hosts down -
Interestingly, the other hosts are getting the rwho broadcasts from the -mm3 box, but the -mm3 box is unable to process rwho broadcasts, including it's own -
Does it use IP multicast? There were recent changes in there. CONFIG_IP_MULTICAST may need to be fiddled with.
Quoted 5 lines · Andrew Morton
Quoted 3 lines · jjs
The symptom here is that running the "ruptime" command on an -mm3 box shows all hosts down -
Quoted 8 lines
Quoted 5 lines
Interestingly, the other hosts are getting the rwho broadcasts from the -mm3 box, but the -mm3 box is unable to process rwho broadcasts, including it's own -
Does it use IP multicast? There were recent changes in there.
CONFIG_IP_MULTICASTmay need to be fiddled with.
It only uses normal ip broadcast AFAIK -
I don't see a solaris-like "-m" option in the
linux man page for rwhod -
Joe