Clovertech

route to /dev/null

› Clovertech Forums › Read Only Archives › Cloverleaf › Cloverleaf › route to /dev/null

  • Creator
    Topic
  • April 17, 2006 at 6:21 pm #48471
    Daniel Lee
    Participant

      Using Qvdxi 3.8.1P on AIX 5.1.

      Is there a way that I can set up my thread to route to /dev/null without creating an extra file thread to write to /dev/null?

      I have a receive interface that is receiving several message types I don’t need to route to anyone.  I’d like to route the message types I need to the sending thread but throw the rest of the message types away.  How can I do this without creating a extra thread to write to /dev/null?  If I just leave them unrouted they’ll junk up my error logs.

    • Creator
      Topic
    Viewing 6 reply threads
    • Author
      Replies
      • April 17, 2006 at 6:24 pm #58712
        Daniel Lee
        Participant

          I think I just thought of an answer for this.  I’ll route them all to the same destination thread but use a different route for the message types I want to throw away.  For the route I want to throw away I’ll just put a proc in the middle that kills all transactions.

        • April 17, 2006 at 7:55 pm #58713
          Keith McLeod
          Participant

            Route them back to the source thread and put a prexlate hcitpsmsgkill proc in place.  This way it doesn’t display in the route properties on the arrow of netmonitor, yet it kills the ones you don’t want.

          • April 17, 2006 at 9:00 pm #58714
            Charlie Bursell
            Participant

              Simple.  Put in an IB proc with the ,ast statement as:  return “{KILL $mh}”

            • April 19, 2006 at 4:38 pm #58715
              Rentian Huang
              Participant

                Charlie, if you put return “{KILL $mh}” as the last statement in IB proc, you are basically killing all msgs, right?

                sam

              • April 19, 2006 at 4:39 pm #58716
                Charlie Bursell
                Participant

                  Yes

                • April 19, 2006 at 4:45 pm #58717
                  Rentian Huang
                  Participant

                    But was it what Daniel wants? I guess he only needs to kill certain transactions not all..

                  • April 24, 2006 at 1:57 pm #58718
                    Terry Kellum
                    Participant

                      If you’re sure that you don’t want to be bothered by non-routed messages in a process, I have used the trick before of setting a raw route to a single /dev/null thread.  That way ALL messages are routed somewhere, and you don’t get errors for non-routed messages.  You can pick what you want and let the rest run to air.

                  • Author
                    Replies
                  Viewing 6 reply threads
                  • The forum ‘Cloverleaf’ is closed to new topics and replies.