IBM Aspera HST Admin Manual page 72

High-speed transfer server
Table of Contents

Advertisement

Note: When a directory is excluded, directories and files in it are also excluded and are not compared to any
following rules.
3. If the file does not match, it is compared to the next rule and repeats the process for each rule until a match is
found or until all rules have been tried.
4. If the file never matches any exclude rules, it is included in the transfer.
5. The next file or directory in the transfer list is then compared to the filtering rules until all eligible files are
evaluated.
Rule Patterns
Rule patterns (globs) use standard globbing syntax that includes wildcards and special characters, as well as several
Aspera extensions to the standard.
Character case: Case always matters, even if the file system does not enforce such a distinction. For example, on
Windows FAT or NTFS file systems and macOS HPFS+, a file system search for "DEBUG" returns files "Debug"
and "debug". In contrast, Ascp filter rules use exact comparison, such that "debug" does not match "Debug". To
match both, use "[Dd]ebug".
Partial matches: With globs, unlike standard regular expressions, the entire filename or directory name must
match the pattern. For example, the pattern abc*f matches abcdef but not abcdefg.
For details on using wildcards and special characters to build rule patterns, see
Files
on page 126.
Set Rules
Filter rules can be set in aspera.conf in the following ways:
by modifying aspera.conf with the asconfigurator tool
by modifying aspera.conf directly with a text editor
In order to run asconfigurator successfully, you must meet the following requirements:
1. have write access to aspera.conf
2. not be restricted to aspshell, which does not allow running asconfigurator
The set commands for user, group, and global filter settings use the following syntax:
asconfigurator -x
"set_user_data;user_name,username;file_filters,|rule1|rule2...|ruleN"
asconfigurator -x
"set_group_data;group_name,groupname;file_filters,|rule1|rule2...|ruleN"
asconfigurator -x "set_node_data;file_filters,|rule1|rule2...|ruleN"
Where:
Each rule argument, including the first, must begin with a "|" character, which serves as the separator between
multiple rules.
To clear rules, run asconfigurator by specifying "file_filters," without rule arguments. Note that the
comma in "file_filters," is still required. See the example below.
Running asconfigurator replaces the specified settings; it does not add to them.
To edit aspera.conf, open it from the following location:
/opt/aspera/etc/aspera.conf
See the following examples for the correct syntax.
Examples
| Configure the Server from the Command Line | 72
Using Filters to Include and Exclude

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents