The bug, shown below, has its origin in Linux sources. I didn't check all the applications of ib_diag package, but at least ibping returns sometimes inconventional return codes. For example, -1 on error instead of a positive value. Or 2 upon 'ibping -V'. Why is it error at all ? And why 2 ? It's ENOENT. Should be EINVAL (22) if it is regarded as error.
I think, it should be fixed both in Linux and Windows in the same way. > -----Original Message----- > From: [email protected] > [mailto:[email protected]] > Sent: Monday, January 04, 2010 4:54 PM > To: Leonid Keller > Subject: [Bug 1886] New: rc of ibping > > https://bugs.openfabrics.org/show_bug.cgi?id=1886 > > Summary: rc of ibping > Product: OpenFabrics Windows > Version: WinOF 2.0 > Platform: All > OS/Version: All > Status: NEW > Severity: normal > Priority: P3 > Component: mlx4 driver > AssignedTo: [email protected] > ReportedBy: [email protected] > CC: [email protected] > > > In the ibping tool, there is a cr (return code) different > from o (zero) on a legal choices. > For example: ibping -V return the code 2 and not 0 as expected. > > > -- > Configure bugmail: > https://bugs.openfabrics.org/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- You are > the assignee for the bug, or are watching the assignee. > _______________________________________________ ofw mailing list [email protected] http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ofw
