You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a Developer I want that the password store shared memory segment's name is configurable so that I can build packages and run X-Road software on the same host
#1355
Currently, the password store shared memory segment's name is hard coded which causes problems in case X-Road packages are built, and X-Road software is run on the same host. This may lead to a situation where the password store shared memory segment gets locked and building packages or running the X-Road software fails. If the password store shared memory segment's name was configurable, such a problem wouldn't exist.
The problem applies to X-Road’s native build only - when the build is run on the host machine. Instead, if the build is run inside a Docker container (./build_packages.sh -d), the problem doesn’t exist.
Currently, the password store shared memory segment's name is hard coded which causes problems in case X-Road packages are built, and X-Road software is run on the same host. This may lead to a situation where the password store shared memory segment gets locked and building packages or running the X-Road software fails. If the password store shared memory segment's name was configurable, such a problem wouldn't exist.
The problem applies to X-Road’s native build only - when the build is run on the host machine. Instead, if the build is run inside a Docker container (
./build_packages.sh -d
), the problem doesn’t exist.This Knowledge Base article contains more information about the error:
https://nordic-institute.atlassian.net/wiki/pages/viewpage.action?pageId=4916422
The JIRA ticket this issue was created from can be found here: https://nordic-institute.atlassian.net/browse/XRDDEV-289
Acceptance criteria:
The text was updated successfully, but these errors were encountered: