lu_pull

March 26, 2020 Contributors

Name

lu_pull — update the Live Updates database

Synopsis

/opt/msys/ecelerity/bin/lu_pull [ –ad_update_only | -a ]

/opt/msys/ecelerity/bin/lu_pull [ –ad_updatesdir /path/to/updatesdir ]

/opt/msys/ecelerity/bin/lu_pull [ –feedback /path/to/feedback_dir ]

/opt/msys/ecelerity/bin/lu_pull [ –help ]

/opt/msys/ecelerity/bin/lu_pull [ –license /path/to/license ]

/opt/msys/ecelerity/bin/lu_pull [ –product productname ]

/opt/msys/ecelerity/bin/lu_pull [ –proxy proxy_url –proxy_user username –proxy_password password ]

/opt/msys/ecelerity/bin/lu_pull [ –updatesdir /path/to/updatesdir ]

/opt/msys/ecelerity/bin/lu_pull [ –url update_url ]

/opt/msys/ecelerity/bin/lu_pull [ –version version_number ]

Description

The lu_pull command is used to update the Live Updates database either for bounce or adaptive rules.

–ad_update_only

Update adaptive rules only.

–ad_updatesdir *`/path/to/updatesdir`*

Override the default adaptive rules location, /opt/msys/ecelerity/etc/msys.

–feedback *`/path/to/feedback_dir`*

The location of the bounce classification files. The default value for this option is /opt/msys/ecelerity/etc/updates.

–help

Display the command options.

–license *`/path/to/license`*

The default value for this option is /opt/msys/ecelerity/etc/license. Use this option to overrride the default.

–product *`productname`*

Override the default productname. The default value for this option is ecelerity.

–proxy *`proxy_url`* –proxy_user *`username`* –proxy_password *`password`*

If you are using a proxy server to access updates use this option to specify the proxy server and your credentials. Use of a proxy server with live updates is discussed in Using a Proxy Server.

–url *`update_url`*

Override the default update URL. The default for this option is https://support.messagesystems.com.

–updatesdir *`/path/to/updatesdir`*

Override the default update directory. The default value for this option is /opt/msys/ecelerity/etc/updates.

–version *`version_number`*

Override the product version of the installation. For example, if you would like to run lu_pull from a 3.2 installation to pull down a 3.0 update, you can do that using this option. This is strictly for testing purpose. We do not support using it in production.

See Also

“adaptive – Adaptive Delivery”