VCS启动+编译过程很慢

ZhengQC

简而言之，是主机名的问题。
使用虚拟机安装REHL/CentOS/RockyLinux/AlmaLinux等操作系统过程中修改默认的主机名localhost.localdomain为其他的名称，这个名称不会被同步到/etc/hosts，需要我们手动修改这个文件，将localhost.localdomain替换为当前的主机名。

joshua2784920

This issue is not related to the contents of the /etc/hosts file.
The reason the new version runs more slowly is because it performs additional checks and uses a more complex algorithm.
It also logs information related to the currently running software, license status, and checkouts to the vendor over the network.
Therefore, modifying the /etc/hosts file as a workaround does not fundamentally resolve the issue.
Furthermore, when connected to the internet, all server-related information — such as user ID, software version, execution time, and the feature name requested for checkout — is shared.
Thus, the workaround of modifying the /etc/hosts file is risky and does not free you from slow checkouts.
The solution is very simple and accessible to anyone, but it does require some effort.
All you need is the ability to write and debug a simple shell script.
If you would like a ready-made batch file, I can share it in exchange for something I need.

tracy6969

interesting

gotoibm

joshua2784920 发表于 2025-5-4 15:55
This issue is not related to the contents of the /etc/hosts file.
The reason the new version runs mo ...

can you provide further instructions? thants in advance

joshua2784920

gotoibm 发表于 2025-5-10 22:54
can you provide further instructions? thants in advance

U need to below two functions

A : l_pubkey_verify
B : scl_lc_checkout

You need to fetch functions A and B.
Since 32-bit binaries have too many inconsistencies, only 64-bit binaries should be considered for this process.

Before using the tools, set the user shell environment variable VCS_TARGET_ARCH to linux64.

Within the VCS installation directory, generate a list of ELF 64-bit binaries.
For each binary in the list, use dasm to generate assembly code.
From the generated ***/XX/VVV/AAA.dasm files, locate functions A and B and extract about 100 bytes (approximately 15 lines) starting from the function entry point.
Save this extracted assembly to a file.

From the extracted dasm code, generate a single-line string that contains only the binary instruction codes.
Even if you extract the same number of lines (e.g., 15 lines), the length of the binary string may vary depending on the actual instructions, since the instruction lengths are different.
Adjust the extraction to get approximately 100 bytes of binary code to make their lengths reasonably consistent.

Sort the resulting binary strings. You will typically find about three unique patterns among them.

For example, suppose you extract a pattern like this:

41574989cf41564589c6415541544189d455534889fb4881ec08010000488b87980200004889742418be140000004c894c2410488b80f01c0000488ba8300600

And you want to replace it with:

31c0c389cf41564589c6415541544189d455534889fb4881ec08010000488b87980200004889742418be140000004c894c2410488b80f01c0000488ba8300600

Create a replacement pattern file using the syntax for the sfk tool. You can find the exact syntax by searching for how to use sfk replace -bylist.

Assuming your replacement pattern file is named replace.pat, use the following command to apply the patch:

sfk replace -bylist replace.pat -nowarn -yes -dir install_directory

There are four unique patterns for each of function A and B.
So, prepare replace_A.pat and replace_B.pat files respectively, and run:

sfk replace -bylist replace_A.pat -nowarn -yes -dir install_directory
sfk replace -bylist replace_B.pat -nowarn -yes -dir install_directory



This is not only VCS but all other S family.