|
|
When storing the settings in Settings Browser, an entry for System->Local Directory is stored in a configuration directory / file used by all images (file system-settings.ston in ~/.config/pharo/7.0 on Linux).
AbsolutePathStoredSetting {
#settingNodeIdentifier : '#pharoSystem#userLocalDirectory',
#realValue : [
'home',
'sasiflo',
'Projekte',
'Pharo',
'images',
'Pharo-7.0.0-alpha.build.1053.sha.682f85d.arch.64bit',
'pharo-local'
]
}
Some other paths as pharo-local are also calculated based on this entry.
Running just one image at the time is no problem, the value UserLocalDirectory is calculated at startup of the image. The entry is updated to a path for the running image. But when running two images in parallel, the second one throws some errors and reads the setting for UserLocalDirectory from the first running image, because that is stored in system-settings.ston.
The notifications are vanishing to fast. It is something about "cannot update ...". I assume it could not write to the system-settings.ston file.
My environment is Debian (buster/sid) Linux 64 Bit and recent Pharo 7.0 / 64 Bit (checked build 1050 -> 1053).
Generally sharing configuration entries as the standard-case is ok and very convinient. But some settings should not be shared. This is one of them I assume.
Problem is, that relocating the UserLocalDirectory with a setting maybe needed. And if set in system-settings.ston there is no way to check if it was set by the running image or another one running in parallel.
|
|
|
Priority: 5 – Fix If Time
|
|
Status: Work Needed
|
|
Assigned to: Everyone
|
|
Milestone: Later
|
Go to Case
|
|
Locked
_Inbox: Not Spam
• You are subscribed to this case
