Difference between revisions of "OS4X Directory Scanner"
| Line 7: | Line 7: | ||
== Configuration of scanning tasks == | == Configuration of scanning tasks == | ||
| + | Using the directory scanner needs some configuration via web interface and optionally in addition on the filesystem (if you really want to modify the behaviour more deeply). | ||
| + | |||
| + | [[Image:Queues menu.png]] | ||
| + | |||
| + | The menu entry "Dir.scanner" in the administrative web interface exists if the binary | ||
| + | os4x_ds_dryrun | ||
| + | exists in the installation directory for binaries of OS4X. | ||
=== Menu entry === | === Menu entry === | ||
| Line 20: | Line 27: | ||
=== Enable / disable entry === | === Enable / disable entry === | ||
=== Preview / Dry-run === | === Preview / Dry-run === | ||
| + | == Logging == | ||
== external links == | == external links == | ||
Revision as of 14:19, 3 November 2011
(incomplete / come back later for a final version)
What is the OS4X Directory Scanner?
The goal of the directory scanner is to scan configured directories (without recursion) for new files (older than 60 seconds) and apply a matching pattern on them. If the pattern matches, the file will be moved to the configured outgoing directory and an executable will be started with parameters defined for this directory scanner entry, based on either fix values or dynamic ones.
The OS4X Directory Scanner is available since OS4X 3 in OS4X 3 Core.
Configuration of scanning tasks
Using the directory scanner needs some configuration via web interface and optionally in addition on the filesystem (if you really want to modify the behaviour more deeply).
The menu entry "Dir.scanner" in the administrative web interface exists if the binary
os4x_ds_dryrun
exists in the installation directory for binaries of OS4X.