I grepped for 'error' and 'fail', and scrolled through the last several hours of messages. I switched the Simias log to DEBUG and tail-grepped for 'Cannot find file,' per the above instructions. It's still got the same cute icon but now it is saying 28 items cannot be synchronized. We upgraded the client over to 8.0.0.3, which indicates in its README that it fixed 'xx items not synchronized problems that most users were seeing.' BS. The client doesn't give any error messages in its log. It worked well for three weeks.īut now, like some hidden time bomb, we've had one client that's just started failing in this way, with status of '24 items not synchrnoized' and a cute little exclamation point logo on the folder icon. I have a three-client system for a law firm and we were planning on using iFolder as a secure file-sharing system. Remember to change the 'Simias.log4net' back to 'INFO' when you are done. After you revert it you should check with the web interface to make sure it is gone. In that case I would revert the iFolder to a normal folder and re-create it. If you have thousands then you may have a deeper problem. This works if you only have a few files that are issues.

Then using the web interface upload the files one at a time. The one I prefer is to log into the iFolder web interface and delete the files that are having the issues. You have several options for fixing the issue.

On the server console where you ran the tail command you will see the files the server is missing. Tail -f Simias.log | grep 'Could not find file'įrom your PC having the issue with the 'incomplete synchronization' start the sync. Change directory to the log directory %IFOLDERDirectory%/simias/data/simias/log/Simias.log.Now tail the log file with this grep filter.Edit the file %IFOLDERDirectory%/simias/data/simias/Simias.log4net.Modify the log file level on the server.home/user/passwordsafe/src/pwsafe-1.15.0/src/os/unix/pws_time.cpp:36:3: error: ‘asctime_r’ was not declared in this scope home/user/passwordsafe/src/pwsafe-1.15.0/src/os/unix/pws_time.cpp: In function ‘int pws_os::asctime(TCHAR*, size_t, const tm*)’: home/user/passwordsafe/src/pwsafe-1.15.0/src/os/unix/pws_time.cpp:30:10: error: ‘localtime_r’ was not declared in this scope did you mean ‘localtime64_r’?ģ0 | return localtime_r(tp, result) != nullptr home/user/passwordsafe/src/pwsafe-1.15.0/src/os/unix/pws_time.cpp: In function ‘int localtime64_r(const _time64_t*, tm*)’: But that is your choice as maintainer, not mine :)įails to build on my system, could be something I've done but nothing that I have figured out. Since it simply won't work for linux without I would wait for the fix if I was you rather than making a temporary fix to the PKGBUILD only to have to revert it in the next release. This is a bug in passwordsafe itself that should be reported as such.

Sed 's/#ifdef _FreeBSD_/#if defined(_linux_) || defined(_FreeBSD_)/' -i src/os/unix/pws_time.h Optdepends=('xvkbd: virtual-keyboard support')Ĭonflicts=('passwordsafe-debian' 'pwsafe' 'pwsafe-gui') Makedepends=('zip' 'libxt' 'cmake' 'git') Pkgdesc='Simple & Secure Password Management'ĭepends=('wxwidgets-gtk3' 'yubikey-personalization' 'xerces-c' 'qrencode' 'file') The complete PKGBUILD file will then look like this + sed 's/#ifdef _FreeBSD_/#if defined(_linux_) || defined(_FreeBSD_)/' -i src/os/unix/pws_time.h Essentially the src/os/unix/pws_time.h is missing an or case for linux resulting in time.h not being included and hence the compile errorīy adding the line starting with a plus sign into the PGKBUILD file (plus sign excluded) it will build successfully. There is a problem with the current source.

Pwsafe plk