• 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 Design
  3. PVS floating license

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 125
  • Views 16256
  • 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

PVS floating license

sjeur
sjeur over 5 years ago

Hello 

I would like to know how to kill PVS floating licenses. Only the license number is available e.g. lcl01/1000 .

Thank you in advance.

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 5 years ago

    I don't understand the question. The license will only be consumed if a PVS job is running; if you want to "kill the license", all you have to do is kill the job... (the licensing system really does not hang on to licenses once jobs have finished - if you see this in my experience is because something really is still running).

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • sjeur
    sjeur over 5 years ago in reply to Andrew Beckett

    PVS session got crashed and   job was still running. Later it became the defunct process . 

    Finally i was able to kill it by using parent process ID. 

    Thank you.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • sjeur
    sjeur over 5 years ago in reply to Andrew Beckett

    PVS session got crashed and   job was still running. Later it became the defunct process . 

    Finally i was able to kill it by using parent process ID. 

    Thank you.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • Frank Wiedmann
    Frank Wiedmann over 5 years ago in reply to sjeur

    Take a look at the lmremove command (https://media.3ds.com/support/simulia/public/flexlm108/EndUser/chap7.htm#wp919200).

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 5 years ago in reply to Frank Wiedmann

    However, lmremove is the wrong way to solve this problem (and should only be used with caution; it may also be restricted at some sites too). It's not a defunct process that's the problem (since they consume no resources other than a slot in the process table), more the fact that the parent process was still running. That's what should be killed, and doing that would cause the license to be released.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Frank Wiedmann
    Frank Wiedmann over 5 years ago in reply to Andrew Beckett

    Depending on the way in which the process is killed, it might not be able to release the license properly, so that the license will only become available again after a timeout period. With the lmremove command, the license can be made available immediately in such a situation.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 5 years ago in reply to Frank Wiedmann

    Frank,

    I find this very surprising. In my experience, no matter how the process exits (even with "kill -9" which cannot be caught by a process to detect its own death) the license server always releases the license because the port is closed. I have not seen any need to use lmremove to remove a stuck license for something that has truly exited in many, many years. I don't recall any recent cases where we have needed to suggest that this is used for this purpose.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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