[gpfsug-discuss] Using AFM to migrate files. (Peter Childs) (Peter Childs) - URL encoding for pathnames

[Marc A Kaplan]

Hmmm.... Peeking into the script, it looks like some of AFM uses the 
simple \\ and \n file list escaping convention (the mmapplypolicy default 
with no ESCAPE specified)  ... And other parts use ESCAPE '%'.    Is this 
inconsistency hidden or does the CLI user have to deal with it? 




From:   Loic Tortay <tortay at cc.in2p3.fr>
To:     gpfsug main discussion list <gpfsug-discuss at spectrumscale.org>
Date:   10/22/2016 09:15 AM
Subject:        Re: [gpfsug-discuss] Using AFM to migrate files. (Peter 
Childs) (Peter Childs) - URL encoding for pathnames
Sent by:        gpfsug-discuss-bounces at spectrumscale.org



On 22/10/2016 15:05, Marc A Kaplan wrote:
> RULE .... EXTERNAL LIST ... ESCAPE '%'
> will direct mmapplypolicy to encode pathnames following RFC3986.
> Use ESCAPE '%/@'  or similar for a more "relaxed" encoding.
>
> See the "Information lifecycle management" chapter of the official pubs
> for more details.
> Read the section that begins ...
>
> ESCAPE '%SpecialCharacters'
> Specifies that path names and the SHOW('string') expressions within the
> associated file lists are
> encoded with a scheme based on RFC3986 URI percent encoding.
>
Hello,
I've read (and used many times) that part of the fine documentation.
My issue is with the documentation of what "mmafcmtl prefetch" expects.


Loïc.
-- 
|     Loïc Tortay <tortay at cc.in2p3.fr>  -  IN2P3 Computing Centre      |

[attachment "smime.p7s" deleted by Marc A Kaplan/Watson/IBM] 
_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20161022/9a67518e/attachment-0002.htm>