Anti-Cryptor doesn't start on OS boot [KES for Linux]

Problem

Sometimes Anti-Cryptor task in KESL won't be able to launch after the OS is started. This may happen because Anti-Cryptor needs all the protected network resources to be up before KESL service is started. In other words, Samba or NFS services should be started before KESL service. 

Solution

To resolve this problem you need to make sure that services start in the correct order.

For Systemd systems:

1. Create a file /etc/systemd/system/kesl.service.d/override.conf

2. Add the following to /etc/systemd/system/kesl.service.d/override.conf:

3. Reload services

For Sys V init systems: 

Rename Samba and NFS init files to make those services start earlier. E.g.

Where <smb_init_file> and <nfs_init_file> stand for current init files present in the system. NFS init file may have different name depending on your environment - nfs, nfs3 or nfs-server.