> A link would not work because the network filesystem is not mounted. > Later on the filesystem is mounted as user and the access rights are too > restricted.
Where is the filesystem mounted as user? Is it mounted on the same dir for all users, or the path is different per user? E.g. is it mounted on /media/network-share, or on /home/$USER/network-share? In the first case, the symlink will work even if the share is mounted on login. If it depends on $USER, yeah symlinks won't help there. But then you would need to dynamically specify the epoptes certificate location too, on user login. Are you using a script for that? If so, can you paste the lines that set SERVERKEY and SERVERCRT? -- You received this bug notification because you are a member of Epoptes Developers, which is subscribed to Epoptes. https://bugs.launchpad.net/bugs/1400807 Title: Certificate / key dir is not configurable Status in Epoptes: Incomplete Bug description: Hallo, I like epoptes. It is fast and easy to use. I administer a school network with multiple computer labs. So the group teachers is maintained on a server and it would make configuration of computers much easier, if I could use a network share to host the certificates public and the keys private for the teachers group. I created a patch for this. I'm not sure if this is the correct way to submit my request and my patch. Please consider including the patch into epoptes. Greetings, Frank Schütte To manage notifications about this bug go to: https://bugs.launchpad.net/epoptes/+bug/1400807/+subscriptions -- Mailing list: https://launchpad.net/~epoptes Post to : [email protected] Unsubscribe : https://launchpad.net/~epoptes More help : https://help.launchpad.net/ListHelp
