[gpfsug-discuss] Question about Policies - using mmapplypolicy/EXTERNAL LIST/mmxargs
Jonathan Buzzard
jonathan.buzzard at strath.ac.uk
Sun Dec 29 10:01:16 GMT 2019
On 28/12/2019 19:49, Marc A Kaplan wrote:
> The script in mmfs/bin/mmxargs handles mmapplypolicy EXTERNAL LIST file
> lists perfectly. No need to worry about whitespaces and so forth.
> Give it a look-see and a try
>
Indeed, but I get the feeling from the original post that you will need
to mung the path/file names to produce a new directory path that the
files is to be moved to. At this point the whole issue of "wacky"
directory and file names will rear it's ugly head.
So for example
/gpfs/users/joeblogs/experiment`1234?/results *-12-2019.txt
would need moving to something like
/gpfs/users/joeblogs/experiment`1234?/old_data/results *-12-2019.txt
That is a pit of woe unless you are confident that users are being
sensible, or you just forget about wacky named files.
In a similar vein, in the past I have for results coming of a piece of
experimental equipment ziped up every 30 days. Each run on the equipment
and the results go in a different directory/ So for example the directory
/gpfs/users/joeblogs/nmr_spectroscopy/2019/results-1229-01/
would be zipped up to
/gpfs/users/joeblogs/nmr_spectroscopy/2019/results-1229-01.zip
and the original directory removed. This works well because both widows
explorer and finder will allow you to click into the zip files to see
the contents. However the script that did this worked in the principle
of a very strict naming convention that if was not adhered to would mean
the folders where not zipped up.
Given the original posters institution, a good guess is that something
like this is what is wanting to be achieved.
JAB.
--
Jonathan A. Buzzard Tel: +44141-5483420
HPC System Administrator, ARCHIE-WeSt.
University of Strathclyde, John Anderson Building, Glasgow. G4 0NG
More information about the gpfsug-discuss
mailing list