FLAM Issue Tracker - CLE/P
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0000182CLE/P1. CLEpublic2013-09-22 12:212013-09-22 12:27
ReporterFalk Reichbott 
Assigned ToFalk Reichbott 
PriorityimmediateSeveritymajorReproducibilitysometimes
StatusresolvedResolutionfixed 
PlatformGeneralOSGeneralOS VersionGeneral
Product Version1.0 
Target Version1.1Fixed in Version1.1 
Summary0000182: Set of enviroment variables over the config file sometimes does not work
DescriptionThe LANG variable can be set, but this Setting is not realised.
Steps To ReproduceSometimes it works but often the value is lost.
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2013-09-22 12:21Falk ReichbottNew Issue
2013-09-22 12:21Falk ReichbottStatusnew => assigned
2013-09-22 12:21Falk ReichbottAssigned To => Falk Reichbott
2013-09-22 12:27Falk ReichbottNote Added: 0000115
2013-09-22 12:27Falk ReichbottStatusassigned => resolved
2013-09-22 12:27Falk ReichbottFixed in Version => 1.1
2013-09-22 12:27Falk ReichbottResolutionopen => fixed

Notes
(0000115)
Falk Reichbott   
2013-09-22 12:27   
Depending on the platform and operating system version, the variable env string in the putenv() function is copied or direct used. The implementation in CLE use a local variable to build the env string based on the key word and value ("keyword=value"). This kind of implementation requires that the env variable must be copied by the system. Now we have changed the implementation and we use a variable which is part of the config list structure. Based on that, the copy is not required anymore. This implementation is mutch more platform indepentant. By the we we have add some more checks if the value was realy set. With the build-in function GETENV you can now verify that this mechanismn works.