Stats

  • Locked Locked
  • Replies 5
  • Subscribers 143
  • Views 14162
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

How to let the messages not show in shell terminal when use ipcBeginProcess ?

Charley Chen

Hello All,

I use  ipcBeginProcess to do something , but I don't want the messages show in xterm , 

How to do it ?

 

Thank you,

Charley 

Parents
  • Andrew Beckett

    Charley,

    Presumably you didn't actually use those calls, because the function has a capital P  in Process, the second argument should be a string (e.g. "") rather than nil, and the log file name is the 6th argument, not the 5th (the 5th is an exit handler).

    If I use:

    procedure(MyDisplayStuff(cid data) printf("STUFF: %L\n" data))
    procedure(MyExitHandler(cid status) printf("EXITED: %L\n" status))
    ipcBeginProcess("/bin/ls" "" 'MyDisplayStuff 'MyDisplayStuff 'MyExitHandler "log")

    Then I get nothing in the terminal, but I do get a file called log. If the file "log" is not writable for some reason, I get this in the xterm:

      Server: could not open/create logfile log

    Is that what you mean?

    Andrew.

Reply
  • Andrew Beckett

    Charley,

    Presumably you didn't actually use those calls, because the function has a capital P  in Process, the second argument should be a string (e.g. "") rather than nil, and the log file name is the 6th argument, not the 5th (the 5th is an exit handler).

    If I use:

    procedure(MyDisplayStuff(cid data) printf("STUFF: %L\n" data))
    procedure(MyExitHandler(cid status) printf("EXITED: %L\n" status))
    ipcBeginProcess("/bin/ls" "" 'MyDisplayStuff 'MyDisplayStuff 'MyExitHandler "log")

    Then I get nothing in the terminal, but I do get a file called log. If the file "log" is not writable for some reason, I get this in the xterm:

      Server: could not open/create logfile log

    Is that what you mean?

    Andrew.

Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.