Branch: refs/heads/master Home: https://github.com/zanata/zanata-platform Commit: 25c45d1502300ce3c36ff5ca0842a1d85a93e41b https://github.com/zanata/zanata-platform/commit/25c45d1502300ce3c36ff5ca0842a1d85a93e41b Author: Sean Flanigan <sflan...@redhat.com> Date: 2017-09-12 (Tue, 12 Sep 2017)
Changed paths: M server/services/src/main/java/org/zanata/ZanataInit.java Log Message: ----------- fix(ZNTA-1786): just warn if lock files are found on NFS (#513) This avoids the need to manually delete lock files, which is nearly always too paranoid for a non-clustered application. Until we set up clustering, it should be safe to delete the lock files, even on NFS, as long as there are other ways of avoiding multiple instances of Zanata (eg some sort of native process/service management). But we log a warning just in case.
_______________________________________________ zanata-commits mailing list firstname.lastname@example.org https://www.redhat.com/mailman/listinfo/zanata-commits