Sign In with your
Trend Micro Account
Need Help?
Need More Help?

Create a technical support case if you need further support.

Modifying the ServerProtect for Linux (SPLX) startup timing to avoid conflicts with third party drivers

    • Updated:
    • 26 May 2014
    • Product/Version:
    • ServerProtect for Linux 3.0
    • Platform:
    • Linux - Red Hat RHEL 3 32-bit
    • Linux - SuSE version 9
Summary
There are rare occasions when a third party module freezes or fails to load when the SPLX kernel modules are loaded.
Examples are the openibd and ipmi drivers, which freeze during bootup when SPLX loads before these modules. If SPLX kernel modules are not loaded or are loaded after openibd and ipmi drivers have started, then the machine will not encounter any issue.
Details
Public
The fastest way to address this issue is to modify the timing as to when the SPLX kernel module will execute. Preferably, the execution should take place after the conflicting module has started and before the network service starts.
Note: Generally, this configuration will not compromise the security level that SPLX will provide to the system because it only monitors the file system for malware entering the system. Before the network is enabled, there is very little chance that these malware can get into the system.

Here is the procedure to adjust the timing:

  1. Look for the service name that owns the conflicting module. For example, "myservice".
  2. Go to "/etc/init.d/rc3.d/" or "/etc/init.d/rc5.d/" (depends on the runlevel setting in "/etc/inittab" file).
  3. Look for the "S<MN>myservice" file.
    If it is "S12myservice", then the number "12" indicates the order when this service will be started.
  4. Locate the "S<XY>splx" file.
    Generally, it is "S01splx", but in some cases, it may be "S50splx".
  5. Locate the "S<AB>network" file.
  6. Rename "S01splx" to "S<CD>splx".
    Where: "CD" is a number bigger than "MN" but smaller than "AB".
  7. Reboot the machine to verify that the issue has been resolved.
  8. After rebooting successfully, check the SPLX status by running the following: 
       "/etc/init.d/splx status"
Premium
Internal
Rating:
Category:
Troubleshoot
Solution Id:
1038050
Feedback
Did this article help you?

Thank you for your feedback!

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support


To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.


Need More Help?

Create a technical support case if you need further support.