sudo /etc/init.d/nilvrt stop

  sudo /etc/init.d/nilvrt start

• LabVIEW debugging tools are not available for copies of reentrant VIs executing on RT targets. Because LabVIEW identifies copies of reentrant VIs by their front panels and VIs executing on RT targets do not include front panels, LabVIEW cannot open reentrant VI copies for debugging.

• http://zone.ni.com/reference/en-XX/help/370622N-01/lvrtconcepts/rt_rtlinux/

• http://www.ni.com/tutorial/14669/en/

• “the System Ressource free physical property node is using the /proc/meminfo command to report the free memory, which does not take disk buffers and caches into account. Especially with logging applications it could look like a memory leak.”
• https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000P9usSAC&l=de-DE
• https://forums.ni.com/t5/LabVIEW/System-Resources-Memory-property-versus-shared-variable-NI/td-p/3778442
• http://blog.scoutapp.com/articles/2010/10/06/determining-free-memory-on-linux

The kernel warning FAT-fs (nvme0n1p1): Volume was not properly unmounted usually indicates that the FAT boot partition was not cleanly unmounted, for example after a power loss. It does not normally require reformatting the disk. Unmount the partition, repair it, verify the result, and mount it again:

umount /dev/nvme0n1p1
fsck.fat -a /dev/nvme0n1p1
fsck.fat -n /dev/nvme0n1p1
mount /dev/nvme0n1p1 /media/nvme0n1p1

After a clean reboot, the warning should no longer appear in the kernel log.