PxPlus User Forum

Main Board => Discussions => Language => Topic started by: James Zukowski on September 08, 2025, 04:45:53 PM

Title: *INIFILE
Post by: James Zukowski on September 08, 2025, 04:45:53 PM
We're looking at using an INI file on our Linux server for some startup information. The documentation indicates the file spec can include a path, but that doesn't seem to be the case. It also doesn't look for the file in the same directory as the executable, which is what we would expect if no path is specified. It's actually in the user launch (home) directory. (We've got that part under control, btw)

Is there something wrong in the usage? The documentation? Other? We're using v15.10 (I know...) on RHEL 7 through WindX.
Title: Re: *INIFILE
Post by: James Zukowski on September 09, 2025, 06:07:43 PM
After resetting a few things, including restarting a new session, it looks like all is working as documented.

(Still curious about the default path, though...)
Title: Re: *INIFILE
Post by: Devon Austen on September 10, 2025, 10:18:20 AM
By design the Linux PxPlus will

Look for <exename>.ini in current directory

and if not found

Look for <exename>.ini in directory where exe resides
Title: Re: *INIFILE
Post by: James Zukowski on September 10, 2025, 10:43:15 AM
It seems to follow the same search logic for non-exename ("mystuff.ini") files as well, instead of the prefix sequencing.