Number of icfb executables running

My guess would be that the log file numbering is sequential (the default) and that it is limited to 10?  You could try starting icfb with the -log switch to specify a different file name/location for the CDS.log file, or use the following:

setenv  CDS_LOG_VERSION  pid

I hope that this helps you.

Regards,
Lawrence.

 How much physical and swap memory do you have on that machine?  Just launching (IC6.1 virtuoso in my case) takes up ~100MB.  Start opening any kind of design data in each of those session and you're going to get to ~200MB per session pretty quickly.  If you don't have enough swap space you're going to run out pretty quickly.

Andrew.

 Cool!  Didn't know about that 'CDS_LOG_VERSION' variable.

Learn something new every day. :-)

Andrew.

Thank you Lawrence,

The CDS_LOG_VERSION =pid worked perfectly.

Regards, 

mims 

The CDS_LOG_PATH environment variable holds a list of the directories in which the CDS.log file is saved into the first writable directory.

If CDS_LOG_VERSION is set to "sequential" how can I find the file name of the current CDS.log file?

Incrementing a counter and checking if each log file exists won't work because that just gives the newest CDS.log unless some were deleted, while I need the current CDS.log file.

Alan,

hiGetLogFileName()

will do what you want.

Regards,

Andrew.

More the number of icfb more the amount of VM used. File->Close data does not release the memory to system pool. If one of the session opened something really big then untill the session is closed your memory is blocked with that session. Be very cautious with multiple sessions.

 There also may be an operating system limit on how manyopen files you can have. This will often be the limiting factor and may not generate any error message. Use the ulimit -a command to see the number of files you are allowed to have open at one time. Remeber that there may be even more files open than just the log file and the current cellView.

Ted