<html><body><p><font size="2">Correct, you may need to use similar parsing/quoting techniques in your renaming scripts.</font><br><font size="2">0</font><br><font size="2">Just remember, in Unix/Posix/Linux the only 2 special characters/codes in path names are '/' and \0. The former delimits directories and the latter marks the end of the string.<br>And technically the latter isn't ever in a path name, it's only used by system APIs to mark the end of a string that is the pathname argument.</font><br><br><font size="2">Happy New Year,</font><br><br><img width="16" height="16" src="cid:1__=0ABB0E4CDFDD4B0D8f9e8a93df938690918c0AB@" border="0" alt="Inactive hide details for Jonathan Buzzard ---12/29/2019 05:01:31 AM---On 28/12/2019 19:49, Marc A Kaplan wrote: > The script i"><font size="2" color="#424282">Jonathan Buzzard ---12/29/2019 05:01:31 AM---On 28/12/2019 19:49, Marc A Kaplan wrote: > The script in mmfs/bin/mmxargs handles mmapplypolicy EXT</font><br><br><font size="2" color="#5F5F5F">From: </font><font size="2">Jonathan Buzzard <jonathan.buzzard@strath.ac.uk></font><br><font size="2" color="#5F5F5F">To: </font><font size="2">"gpfsug-discuss@spectrumscale.org" <gpfsug-discuss@spectrumscale.org></font><br><font size="2" color="#5F5F5F">Date: </font><font size="2">12/29/2019 05:01 AM</font><br><font size="2" color="#5F5F5F">Subject: </font><font size="2">[EXTERNAL] Re: [gpfsug-discuss] Question about Policies - using mmapplypolicy/EXTERNAL LIST/mmxargs</font><br><font size="2" color="#5F5F5F">Sent by: </font><font size="2">gpfsug-discuss-bounces@spectrumscale.org</font><br><hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><br><br><br><tt><font size="2">On 28/12/2019 19:49, Marc A Kaplan wrote:<br>> The script in mmfs/bin/mmxargs handles mmapplypolicy EXTERNAL LIST file <br>> lists perfectly. No need to worry about whitespaces and so forth.<br>> Give it a look-see and a try<br>> <br><br>Indeed, but I get the feeling from the original post that you will need <br>to mung the path/file names to produce a new directory path that the <br>files is to be moved to. At this point the whole issue of "wacky" <br>directory and file names will rear it's ugly head.<br><br>So for example<br><br>/gpfs/users/joeblogs/experiment`1234?/results *-12-2019.txt<br><br>would need moving to something like<br><br>/gpfs/users/joeblogs/experiment`1234?/old_data/results *-12-2019.txt<br><br>That is a pit of woe unless you are confident that users are being <br>sensible, or you just forget about wacky named files.<br><br>In a similar vein, in the past I have for results coming of a piece of <br>experimental equipment ziped up every 30 days. Each run on the equipment <br>and the results go in a different directory/ So for example the directory<br><br>/gpfs/users/joeblogs/nmr_spectroscopy/2019/results-1229-01/<br><br>would be zipped up to<br><br>/gpfs/users/joeblogs/nmr_spectroscopy/2019/results-1229-01.zip<br><br>and the original directory removed. This works well because both widows <br>explorer and finder will allow you to click into the zip files to see <br>the contents. However the script that did this worked in the principle <br>of a very strict naming convention that if was not adhered to would mean <br>the folders where not zipped up.<br><br>Given the original posters institution, a good guess is that something <br>like this is what is wanting to be achieved.<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></font></tt><tt><font size="2"><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</a></font></tt><tt><font size="2"> <br><br></font></tt><br><br><BR>
</body></html>