#1 Jicofo should not need write access to its config dir
Closed 4 years ago by lcts. Opened 4 years ago by lcts.

Moved from https://pagure.io/fedora-rpm-addons/issue/4.

Currently, jicofo errors if it doesn't have write access to its config dir despite not actually writing anything to it.


The issue with missing write permission for jicofo in /etc/jicofo is neglectable.
I looked into the source and found out, that net.java.sip.communicator.impl.configuration.ConfigurationActivator
tries to "fix" permissions. It catches the resulting exception however and just logs
a very confusing error message (See here).

Metadata Update from @felfert:
- Issue assigned to felfert

4 years ago

In the meantime, I reading source some more, I figured it out, how this is properly solved:

  • In /etc/jicofo/config, the homedir must be set properly:
 -Dnet.java.sip.communicator.SC_HOME_DIR_LOCATION=/run\
 -Dnet.java.sip.communicator.SC_HOME_DIR_NAME=jicofo\
  • in the startup shell wrapper, before executing java, /etc/jicofo/sip-communicator.properties has to be copied into ~/ in order to be picked up.

Will make the appropriate changes together with permission fixes mentioned in #5
and submit another PR...

Metadata Update from @felfert:
- Assignee reset

4 years ago

PR #12 fixing this issue has been merged.

Metadata Update from @lcts:
- Issue status updated to: Closed (was: Open)

4 years ago

Log in to comment on this ticket.

Metadata
Related Pull Requests
  • #12 Merged 4 years ago