All of lore.kernel.org
 help / color / mirror / Atom feed
From: Edward Mascarenhas <eddiem-sJ/iWh9BUns@public.gmane.org>
To: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	EWG <Openfabrics-ewg-0P3JtQMG0aQdnm+yROfE0A@public.gmane.org>
Cc: kliteyn-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org
Subject: ibdiagpath return code incorrect
Date: Fri, 16 Oct 2009 16:15:54 -0700	[thread overview]
Message-ID: <4AD8FEAA.101@sgi.com> (raw)

It appears that even on error ibdiagpath is returning zero but it
should return non-zero for error cases. Scripts that call ibdiagpath
can use the return code to take appropriate action.

Here is an example.

==================================================
service0: # ibdiagpath -i 1 -d 1,12
Loading IBDIAGPATH from: /usr/lib64/ibdiagpath1.2
-W- Topology file is not specified.
    Reports regarding cluster links will use direct routes.
Loading IBDM from: /usr/lib64/ibdm1.2
-I- Using port 1 as the local port
    (since that is the output port based on the provided direct route).

-I---------------------------------------------------
-I- Traversing the path from local to destination
-I---------------------------------------------------
-I- From: lid=0x000c guid=0x0002c90200291949 dev=25218 service0/P1
-I- To:   lid=0x001d guid=0x0800690000005264 dev=48438 Port=28


can't read "PATH(1)": no such element in array

service0:/tmp/src # echo $?
0
service0:/tmp/src #
================================================

Assuming this is a bug, I don't have a fix, but I'm hoping someone who
is more familiar with the ibdiagpath code will provide a fix.

Thanks,
Edward

                 reply	other threads:[~2009-10-16 23:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4AD8FEAA.101@sgi.com \
    --to=eddiem-sj/iwh9buns@public.gmane.org \
    --cc=Openfabrics-ewg-0P3JtQMG0aQdnm+yROfE0A@public.gmane.org \
    --cc=kliteyn-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.