![egnyte desktop sync 127.0.0.1 waiting egnyte desktop sync 127.0.0.1 waiting](https://www.egnyte.com/sites/default/files/2020-03/Online_and_offline_access_1.png)
If you run the ‘top’ utility you can seek for the CPU usage and for the CPU I/O waiting time that are represented by the ‘ us‘ and ‘ wa‘ abbriaviations. These values represent CPU, Disk I/O and Network I/O. The Load Avarage values that are shown using the ‘top’ commad or the ‘uptime’ command represent the number of blocking processes in the run queue averaged over a certain time period.Īn example fo HIGH Load Avarage: load average: 12.54, 12.71, 12.19
#Egnyte desktop sync 127.0.0.1 waiting how to#
This is how to set up a continuos synchronization on the background with the Local Group Policy Editor: I have found a workaround to this problem playing a little with the Windows’s Group Policy Editor.Īs I don’t have a Windows Domain in place I couldn’t generate a policy file to be pushed once for all to all the clients so I had to manually start and configure the Group Policy Editor on each single Window VISTA and Windows 7 machine.
#Egnyte desktop sync 127.0.0.1 waiting mac os x#
I understood that because of an obvious delay on the communication from the Windows client through the Mac OS X server (via SMB) to the Linux server (via NFS) would make the Windows client believe that the share was offline with many unconfortable conseguences. I have experienced problem with Windows Clients stopping to synchronize files without any reasonable motivation.
![egnyte desktop sync 127.0.0.1 waiting egnyte desktop sync 127.0.0.1 waiting](https://helpdesk.egnyte.com/hc/article_attachments/360020743672/Screen_Shot_2019-02-07_at_11.32.59_AM.png)
I have a very unadvisable configuration where a Linux server is providing an NFS share to a Mac OS X Snow Leopard server, and that server is then re-sharing via SMB and AFP that share to Windows and Mac OS X clients.
![egnyte desktop sync 127.0.0.1 waiting egnyte desktop sync 127.0.0.1 waiting](https://helpdesk.egnyte.com/hc/article_attachments/360039330012/Screen_Shot_2019-09-24_at_4.04.22_PM.png)
That may confuse some applications, especially Microsoft Office making them believing that a file you just edited and closed is still opened by another application and will refuse to open such file again. I found the latest generation of Windows to be very sensitive in the process to keep synchronized the Offline Files and folders copy with the remote share.ĭepending on the quality of the network you rely or the quality of the link to the share the Windows 7 (or VISTA) clients may think that the share is temporarily unavailable and stop synchronizing the Offline Folder while leaving temporary files on the server.