This is known and fixed in more recent versions. I am guessing you mean you are running 2.3 not 3.3 :).
Benoit Boccard <[email protected]> wrote: >Hi, > >We've noted a strange behaviour when we have special characters (like >^M or >other invisible characters) : >the db seems to be corrupted, but it's only the display, because these >characters are stored in the db. > >For example : > > JobID JobName UID QOS Partition AllocCPUS >NCPUS NNodes NodeList Submit State ExitCode >------------ ---------- ------ ---------- ---------- ---------- >---------- >-------- --------------- ------------------- ---------- -------- >987526 2 1245 seq_court compute 1 >1 1 cn026 2013-03-15T15:27:13 COMPLETED 0:0 > JobID JobName UID QOS Partition AllocCPUS >NCPUS NNodes NodeList Submit State ExitCode >------------ ---------- ------ ---------- ---------- ---------- >---------- >-------- --------------- ------------------- ---------- -------- >987541 *°Ïw * 1245 seq_court Fefs/Zj47+ 1 >1 1 *°Ù¯* 2013-03-15T15:27:13 COMPLETED 0:0 > JobID JobName UID QOS Partition AllocCPUS >NCPUS NNodes NodeList Submit State ExitCode >------------ ---------- ------ ---------- ---------- ---------- >---------- >-------- --------------- ------------------- ---------- -------- >987569 *PäO* 1245 seq_court ^| 1 >1 1 None assigned 2013-03-15T15:27:14 COMPLETED 0:0 > JobID JobName UID QOS Partition AllocCPUS >NCPUS NNodes NodeList Submit State ExitCode > >Do you know if there is a workaround (except educate our users, we're >doing >the maximum for that :-)), or or if there is a bugfix (we use slurm >3.3, >pretty old version). > >Thank you ! > >Regards, >Benoit Boccard
