Why are my changes to seos.ini not being loaded?

Document ID : KB000012160
Last Modified Date : 14/02/2018
Show Technical Document Details
Question:

Why does the endpoint's behavior not get changed after seini is used to change a token and secons -rl is used to reload?

Answer:

The secons -rl command only reloads the seosd daemon. If the token that has been changed affects another daemon, then secons -S must be used to stop that daemon and start it again. If the token affects seagent, the endpoint must be completely stopped and started again. If the token affects the syscall, then the endpoint must be stopped and the syscall must be unloaded and reloaded for the change to take effect.

Additional Information:

For more information regarding the seos.ini file, please refer to the Implementation Guide:

https://docops.ca.com/ca-privileged-identity-manager/12-9/EN/reference/configuration-files/the-seos-ini-initialization-file