<div class="socmaildefaultfont" dir="ltr" style="font-family:Arial, Helvetica, sans-serif;font-size:10pt" ><div dir="ltr" >Hi Ed,</div>
<div dir="ltr" > </div>
<div dir="ltr" >not a ready to run for "everything".. but just to remind, there is an ESCAPE statement</div>
<div dir="ltr" >by this you can</div>
<div dir="ltr" > </div>
<div dir="ltr" > cat policy2 <br>RULE EXTERNAL LIST 'allfiles' EXEC '/var/mmfs/etc/list.exe' ESCAPE '%/#'</div>
<div dir="ltr" ><div class="socmaildefaultfont" dir="ltr" style="font-family:Arial, Helvetica, sans-serif;font-size:10pt" ><div class="socmaildefaultfont" dir="ltr" style="font-family:Arial, Helvetica, sans-serif;font-size:10pt" ><div dir="ltr" ><div> </div>
<div>and turn a file name into smth , what a policy can use</div>
<div> </div>
<div>I haven't used it for a while , but here is an example from a while ago .. ;-)</div>
<div> </div>
<div>[root@c25m4n03 stupid_files]# ll<br>total 0<br>-rw-r--r-- 1 root root 21 Mar 22 03:44 dämlicher filename<br>-rw-r--r-- 1 root root 2 Mar 22 03:59 üöä???ßß spacefilen<br>[root@c25m4n03 stupid_files]#</div>
<div> </div>
<div> </div>
<div>policy:</div>
<div>101378 247907919 0 -- /gpfs/fpofs/files/stupid_files/d%C3%A4mlicher%20filename<br>101381 1945364096 0 -- /gpfs/fpofs/files/stupid_files/%C3%BC%C3%BC%C3%BC%C3%B6%C3%B6%C3%A4%C3%A4%3F%3F%3F%C3%9F%C3%9F%20spacefilename<br>[I]2013-03-22@13:12:58.687 Policy execution. 2 files dispatched. </div>
<div> </div>
<div> verify with policy (ESCAPE '%/ä ')</div>
<div>101378 247907919 0 -- /gpfs/fpofs/files/stupid_files/dämlicher filename<br>[...] </div>
<div> </div>
<div> </div>
<div>hope this helps..</div>
<div>cheers</div>
<div> </div>
<div> </div></div></div></div></div>
<div dir="ltr" > </div>
<div dir="ltr" > </div>
<blockquote data-history-content-modified="1" dir="ltr" style="border-left:solid #aaaaaa 2px; margin-left:5px; padding-left:5px; direction:ltr; margin-right:0px" >----- Ursprüngliche Nachricht -----<br>Von: "Jonathan Buzzard" <jonathan.buzzard@strath.ac.uk><br>Gesendet von: gpfsug-discuss-bounces@spectrumscale.org<br>An: gpfsug-discuss@spectrumscale.org<br>CC:<br>Betreff: [EXTERNAL] Re: [gpfsug-discuss] Handling bad file names in policies?<br>Datum: Di, 5. Okt 2021 01:29<br>
<div><font size="2" face="Default Monospace,Courier New,Courier,monospace" >On 04/10/2021 23:23, Wahl, Edward wrote:<br><br>> I know I've run into this before way back, but my notes on how I solved<br>> this aren't getting the job done in Scale 5.0.5.8 and my notes are from<br>> 3.5. \U0001f609<br>> Anyone know a way to get a LIST policy to properly feed bad filenames<br>> into the output or an external script?<br>><br>> When I say bad I mean things like control characters, spaces, etc. Not<br>> concerned about the dreaded 'newline' as we force users to fix those or<br>> the files do not get backed up in Tivoli.<br>><br><br>Since when? Last time I checked which was admittedly circa 2008, TSM<br>would backup files with newlines in them no problem. mmbackup on the<br>other hand in that time frame would simply die and backup nothing if<br>there was a single file on the file system with a newline in it.<br><br>I would take a look at the mmbackup scripts which can handle such stuff<br>(least ways in >4.2) which would also suggest dsmc can handle it.<br><br>As an aside I now think I know how you end up with newlines in file<br>names. Basically you cut and paste the file name complete with newlines<br>(most likely at the end) into a text field when saving the file.<br>Personally I think any program should baulk at that point but what do I<br>know.<br><br><br>JAB.<br><br>--<br>Jonathan A. Buzzard Tel: +44141-5483420<br>HPC System Administrator, ARCHIE-WeSt.<br>University of Strathclyde, John Anderson Building, Glasgow. G4 0NG<br>_______________________________________________<br>gpfsug-discuss mailing list<br>gpfsug-discuss at spectrumscale.org<br><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss" target="_blank">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</a> </font></div></blockquote>
<div dir="ltr" > </div></div><BR>
<BR>