criproxy failed to start after host reboot

After host reboot, the criproxy failed to start. /var/log/syslog shows the following error msg.

criproxy.service: Failed at step EXEC spawning /tmp/criproxy/criproxy: No such file or directory

Based on the default vars, the criproxy is installed into /tmp directory which refreshes after reboot. So I think we can fix the issue by specify a persistent directory instead of using the default /tmp