...
When Linux starts a service, Linux also runs a startup script. The startup script runs when the machine powers on or when a service manually starts. The startup script startup script typically runs tasks that relate to the starting, stopping, and restarting of a service.
For database services, the startup script startup script typically runs tasks that occur in folders that hold database files. With encrypted database files, you must allow the startup script the startup script to access the database folders. If not, the database will not start properly, and in some cases, interfere with the power on process for the machine.
As part of the startup process, the operating system needs permission to view and change file / folder ownership and permissions. As a result, if you want to guard var/lib/mysql, you must create two rules in your policy.
...
| Note |
|---|
In the instructions below, you will create and add two rules to your policy. |
Log into your DSM as Security as Security Administrator.
In the menu bar, click click Polices, and then click Manage Manage Policies.
Mark the policy that guards your databases, such as as /var/ib/sql/data, and then click click Add.
Under Under Security Rules, click click Add.
Next to to Resource, click click Select.
In the window that appears, click click Add.
In In Name, enter a descriptive name for your Resource Set.
Click Click Add to to specify a resource that will need to be accessed in the GuardPoint upon startup.
- In Directory, enter a slash: \
In In File, enter the mysql.sock file that needs to be accessed upon startup, and then click click Ok. These resource must be added one at a time.
(Optional) To add resources, repeat steps 8 - 10.
Mark the newly created Resource Set, and then click click Select Resource Set. In In the window that appears, Resource is is populated with the newly created Resource Set.
Next to to Effect, click click Select.
Mark Mark Permit and Apply Key.
Click Click Select Effect.
Click Ok.
Mark the rule, and then click click Up to to move the new rule above the catch-all rule.
Note For your reference you have just created and added the first rule. 
Inside your policy editor, click Add to create the second security rule.
Next to Action, click Select.
- Using the image below for, mark all the rules listed below.
Click Select Action.
Next to Effect, click Select.
Mark Permit, and then click Ok.
Click Ok.
Mark the rule, and then click click Up to to move the new rule up one entry.
Click Apply to save, and then click click Ok.
(Optional) You should test to make sure your system is running properly.