Stats

  • Replies 4
  • Subscribers 126
  • Views 91
  • Members are here 0

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

ebecheto

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

Parents
  • Yagya Mishra
    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
Reply
  • Yagya Mishra
    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
Children
  • ebecheto
    in reply to Yagya Mishra

    Thank you Yagya fo the tips.

    That noes not solve my problem though. I thinks my issue is in the locking mechanism, when virtuoso try to acces to directory ~/.cadence

    Do you know if there is an environment variable to specify the ~/.cadence directory to be somewhere else ?

  • ebecheto
    in reply to ebecheto

    I think i found a workaround to my issue: 

    mv .cadence /local/ebecheto/home/
    ln -s /local/ebecheto/home/.cadence/ .cadence

    That prevent wierd files created by the file system : 
    ll .cadence/.nfs0000000111356b54000000ec 
    lsof .cadence/.nfs0000000111356b54000000ec 
    COMMAND     PID     USER   FD   TYPE DEVICE SIZE/OFF       NODE NAME
    virtuoso 117810 ebecheto    8u   REG   0,49        0 4583680852 .cadence/.nfs0000000111356b54000000ec

    I still do not know it the issue is from cadence or from my file system, but at last i have a functional solution.

  • Andrew Beckett
    in reply to ebecheto

    I was going to suggest that you use setup.loc to omit the home directory, but that .nfs file suggests that you have a running process that still has the file open, but the file itself has been deleted. With local file systems if you delete an open file, it's still accessible via the inode - but for an NFS file system it has to keep some kind of handle to it and hence you end up with these .nfs files until the process (117810) ends.

    Perhaps exit that process and the .nfs file should vanish.

    Andrew

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.