Date: Fri, 29 Mar 2024 11:43:37 +0000 (UTC) Message-ID: <1438672272.19.1711712617149@d2df1c7daebb> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_18_1711799018.1711712617149" ------=_Part_18_1711799018.1711712617149 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
PP-668 - execjob_launch fails to setup = the environment properly if one of the environment variables has a \n or a = comma or quotes Closed
Ticket PP-668 - execjob_launch fails to setup t= he environment properly if one of the environment variables has a \n or a c= omma or quotes Closed will= address a problem with execjob_launch hooks in PBS where a job's environme= nt gets truncated if one of the environment variables has a newline (\n), c= omma (,), or single/double quotes appearing as values. The solution involve= s raw string handling of the job's Variable_List, which is used to populate= a job's environment. Currently, when jobs are submitted with the -V = option and there are environment variables with special characters, P= BS already escapes the comma, single/double quotes in values by prefixing t= hem with the backslash (\) in both Linux/Unix and Windows. However, with ex= ecjob_launch hooks enabled, this leads to a problem with Windows in that ba= ckslash is considered a legal pathname character. PP-668 implementation wil= l use caret (^) as the escape character on Windows for the mentioned s= pecial characters. Note that the escape character itself will also = get escaped, appearing as \\ under Linux/Unix and ^^ under Windows.