> Source: [sk130432](https://support.checkpoint.com/results/sk/sk130432)

# sk130432 - Process affinity settings do not survive reboot

| Property | Value |
|----------|-------|
| Solution ID | sk130432 |
| Date Created | 2018-07-02 |
| Last Modified | 2021-05-31 |
| Technical Level | General |
| Products | Security Gateway |
| Versions | R82.10, R82, R81.20 |
| OS | Gaia |

## Symptoms

- * Although the process affinity settings are configured correctly in the *fwaffinity.conf* file, it does not survive reboot.
* Setting the affinity manually after reboot, with the `'fw ctl affinity -s'` command works until next reboot.

## Cause

The script which applies the affinity during boot, is checking the `"ps aux"` output, to verify which processes are up before setting the affinity. Some processes might take some time to come up, so the affinity setting did not applied.

## Solution

[Contact Check Point Support](https://www.checkpoint.com/support-services/contact-support/) to get a Hotfix for this issue.   
A Support Engineer will make sure the Hotfix is compatible with your environment before providing the Hotfix.   
For faster resolution and verification please collect [CPinfo](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk92739) files from the Security Management and Security Gateways involved in the case.

**The code was improved:** The system will verify the affinity of all the daemons\\processes every few seconds.

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content