• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC SKILL
  3. how to kill process in started with ipcbeginprocess

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 143
  • Views 12524
  • 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 kill process in started with ipcbeginprocess

saurabh96
saurabh96 over 4 years ago

Hello Guys,


command=strcat("xterm -ls -hold -e \"./batch -version\"-parentTool virtuoso")
cmdPid = ipcBeginProcess(command)
ipcWait(cmdPid)


Here batch is runfile.
When I am executing the above "command", xterm is launching, and the batch file starts running ...Now, after runs complete, xterm is still there, and the process is still running...or I have to close xterm manually....is their way that xterm close automatically after runs(process) completes??
I appreciate any help you can provide.
Regards,
SRV

  • Cancel
Parents
  • mbracht
    mbracht over 4 years ago

    Hi,

    If that is a batch job then why would you want to run it in an xterm in the first place - I mean why not pass it directly to the ipcBegin.

    In your above command you may replace the "-hold" option of xterm against "+hold" so as to make sure it returns.

    Max

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • mbracht
    mbracht over 4 years ago in reply to mbracht

    Hi,

    If that is a batch job then why would you want to run it in an xterm in the first place - I mean why not pass it directly to the ipcBegin.

    In your above command you may replace the "-hold" option of xterm against "+hold" so as to make sure it returns.

    Max

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • saurabh96
    saurabh96 over 4 years ago in reply to mbracht

    Hi Max,

    Thanks for reply..

    1)am using xterm because when we run runfile it needs user input at some point in between as yes/no as conformation ...using xterm allows to run process on xterm and user can give input while process is running.

    2)  -hold is also running fine..lemme try +hold ;..just i want that as when process completes the xterm should close or process get killed without manually closing xterm

    regards,

    srv

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • mbracht
    mbracht over 4 years ago in reply to saurabh96

    Just run the man page for xterm...

     -hold   Turn on the hold resource, i.e., xterm will not immediately destroy its window when the shell command com-
                   pletes.   It will wait until you use the window manager to destroy/kill the window, or if you use the menu
                   entries that send a signal, e.g., HUP or KILL.

     +hold   Turn off the hold resource, i.e., xterm will immediately destroy its window when the  shell  command  com-
                   pletes.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • saurabh96
    saurabh96 over 4 years ago in reply to mbracht

    Hi Max,

    Thanks and regards..i will surely look it .

    cheers for guidance!

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • saurabh96
    saurabh96 over 4 years ago in reply to mbracht

    Hi Max,

    Thanks and regards..i will surely look it .

    cheers for guidance!

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information