If the DCAF Engine is already running, and you use the deploy tool again and it updates the SO file while the system is running. It might cause a crash as it might override the SO that is being called for syslog.
It appears that the issue is as follow:
Engine starts up and opens the SysLog Libraries
The config tool publishes the new library and overwrites the files on disk
The Engine does something that triggers a Syslog write
LabVIEW RT Crashes
The best options for solving this right now are:
1) Add and option in the tool for Include SO default to true (to maintain existing behavior)
2) Add option for “ignore if present” (or similar), default to true (This will change existing behavior), but allows to redeploy the file if needed.
3) Deployment utility checks if .so file is present prior to deploy. If so, it does not redeploy. If (and only if) it is not present, deploy.
Probably option 1 is the faster to implement and with the lowest risk.
If the DCAF Engine is already running, and you use the deploy tool again and it updates the SO file while the system is running. It might cause a crash as it might override the SO that is being called for syslog. It appears that the issue is as follow:
The best options for solving this right now are: 1) Add and option in the tool for Include SO default to true (to maintain existing behavior) 2) Add option for “ignore if present” (or similar), default to true (This will change existing behavior), but allows to redeploy the file if needed. 3) Deployment utility checks if .so file is present prior to deploy. If so, it does not redeploy. If (and only if) it is not present, deploy.
Probably option 1 is the faster to implement and with the lowest risk.