• 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. can we ask virtuoso to write its lock or CDS.log somewhere...

Stats

  • Replies 1
  • Subscribers 126
  • Views 39
  • Members are here 0

can we ask virtuoso to write its lock or CDS.log somewhere else than $HOME ?

ebecheto
ebecheto 2 hours ago

Symptom of my bug.

I have a machine with a $HOME on a shared NFSv3 network folder.

virtuoso version IC25.1-64b, although it is the same for other versions.

If i ran virtuoso, it freezes the shell.

If i use a local user (with its $HOME in let says a /local/home/user directory) virtuoso ran properly.

Another trick, work too : if I change HOME variable : 

mkdir -p /local/$USER/home/ && cd /local/$USER/home/
cp $HOME/.Xauthority /local/$USER/home/
export HOME=/local/$USER/home
source /share/Adm/license_common.sh
/share/Cad/CAD/IC251/tools/dfII/bin/virtuoso #<= OK DOES NOT FREEZE

Marvellous ! Virtuoso start fast and properly.

Is there an environment variable to set to say to virtuoso to use another fake directory to prevent access to $HOME directory ?

Thanks for sharing thoughts, Regards, Edouard

  • Cancel
  • Sign in to reply
  • Yagya Mishra
    Yagya Mishra 6 minutes ago
    1. You should be able to set default log path using the shell variable

      setenv CDS_LOG_PATH <full_path_name>

    2. You can also provide multiple directories to this shell variable separated by colon (:)  (in order of preference)

      setenv CDS_LOG_PATH /project/logFiles/virtuosoLog/:/home/CAD/user/LOGS:/home/cds/logs

      Note: If none of the directory exists then log file will be created in $HOME

    3. You can also use this shell variable to create log file sequently (CDS.log.1, CDS.log.2,....CDS.log105) rather than
      updating the same CDS.log over and over again.

      setenv CDS_LOG_VERSION sequential
    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • 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