Hi, I see the below scenario. Would like to know if it's an expected behavior or not.
1. Install a VIB which has a file ( say /etc/cim/<dir>/a.txt ) with sticky bit set.
2. After installation and reboot, modify the file by writing something to it. This creates a .#a.txt in the visorFS ( expected as per visorFS design )
3. Now uninstall the VIB
4. After uninstallation and reboot, it is seen that the file still exists in /etc/cim/<dir>/a.txt
Does it mean VIB uninstallation dont take care of removing the .# files and in the next bootup, backup.sh just removes the .# and keep it as the original name?