View Ticket
19:24 Ticket [126a356681] starsync does not update the virtual file system in the local starkit status still Open with 5 other changes artifact: dc9794efbd user: anonymous
19:22 New ticket [126a356681]. artifact: d0bef9731f user: anonymous

Ticket Hash: 126a356681e046c4bb594786e978381c245288e7
Title: starsync does not update the virtual file system in the local starkit
Status: Open Type: Code_Defect
Severity: Critical Priority: Immediate
Subsystem: Resolution: Open
Last Modified: 2018-03-18 19:24:10
Version Found In:
User Comments:
anonymous added on 2018-03-18 19:22:37:
I noticed that my local starkit cannot retrieve the updates from my cgi sync server. Update can perform the first pull from the server if there is no local copy of the starkit. That's great. Also, update can understand there are changes by using -n flag, however, still, the update operation leaves the virtual file system unchanged. A subsequent run of update with -n says there are still changes on the server compared to the local copy, which is true.

I examined the source and possibly found the reason. In 


There is a request procedure. Through the end of the procedure, there is a Mount operation using -nocommit flag: 

vfs::mk4::Mount $path $path -nocommit

If I remove that flag, the issue is resolved. The local copy can receive the updates and a subsequent run with update -n says, there is no change on the server. This seems to work for me now, however, I hope I am not distorting the transactional nature of updates by doing so. It would be great to understand that, and if there is no issue involved remove the nocommit flag from the mount operation.

Dr. Koru
Information Systems