Bug #1778
RCP: 0.7.7, under Windows 7 buggy corpora libcqp access with TXM home directory on shared drive
Status: | New | Start date: | 04/12/2016 | ||
---|---|---|---|---|---|
Priority: | Normal | Due date: | |||
Assignee: | - | % Done: | 80% |
||
Category: | SearchEngine | Spent time: | - | ||
Target version: | TXM 0.7.8 |
Description
Diagnostic based on TXM 0.7.7 installed on Windows 7 64-bit machines in ENS de Lyon F24 class room with Student roaming profile (the user home directory is on a shared drive, there are some access restrictions).
Several behaviors can be observed (depending on the machine):- for TXM first run by the Student profile, TXM can't write corpora files during the postinstall process (wrong access).
- corpora files have been installed but no corpus is loaded at startup (the Corpus view is empty), then 5 minutes later, all corpora appear in the corpus view and can be used by libcqp
- or, corpora files have been installed and all corpora appear in the Corpus view at startup, but no one can be used by libcqp
Solution 1¶
Set TXM home locally
The first time you use TXM on a machine,
- launch TXM :
- set the “TXM > Avancé > Dossier utilisateur TXM” setting to “C:\Users\username\TXM”
- set the “TXM > Avancé > Moteur de Corpus > Chemin vers le répertoire de Registre” setting to “C:\Users\username\TXM\registry” (if present in your TXM)
- quit TXM
- remove any local TXM home directory (C:/Users/username/TXM)
- launch TXM
TXM postinstall process should copy home directory and default corpora locally.
Hypothesis¶
- the CQP file access methods cannot access file on shared disk on network
Solution 2¶
Verify if the new CQP file access methods works with:- network paths (possibly different network paths)
- for high log level (at least ALL), display logs for each file access of libcqp primitives (directory open, read, write, close; file open, read, write, close, etc.)
- if the user profile prevents some file access (for example for writing), display a clear error message before aborting corpus load or import
- update file access primitives of libcqp to better handle network protocols
Result: the "\\" UNC paths are not interpreted by mingw
The solution is to replace the "\\" paths by "//" paths only for paths given to CQP :- the registry paths given to
- the CQP process or CQPlib
- the cwb-encode process
- the data paths given to the registry files when
- registry files are patched (at corpus load command)
Solution 3¶
Use an account with a Profile having local home directory.
History
#1 Updated by Serge Heiden over 7 years ago
- Description updated (diff)
#2 Updated by Serge Heiden over 6 years ago
- Description updated (diff)
- Target version changed from TXM 0.8.0a (split/restructuration) to TXM 0.7.8
#3 Updated by Serge Heiden over 6 years ago
- Description updated (diff)
#4 Updated by Matthieu Decorde over 6 years ago
- Description updated (diff)
#5 Updated by Matthieu Decorde over 6 years ago
- % Done changed from 0 to 80