4Suite repository management tools This command-line application allows a 4Suite repository administrator to perform management tasks on the repository as a whole, including setup, server control, backup, and other operations. `show detailed help message` `show system command tree` `Report on the state of a repository and its servers This command lists the status of each server in a 4Suite repository (running or stopped) as well as the state of the repository itself (data store existence and initialization status). `show detailed help message` `authenticate using the given user name` `authenticate using the given password` `use a specific core in config file (default: Core)` `use alternative repository configuration file`` `Commands to work with the logs Manager commands to work with the log files `show detailed help message` `authenticate using the given user name` `authenticate using the given password` `use a specific core in config file (default: Core)` `use alternative repository configuration file` `Clear a 4SS Log Clear the logs `show detailed help message` `authenticate using the given user name` `authenticate using the given password` `use a specific core in config file (default: Core)` `use alternative repository configuration file`` `View a 4SS Log View the logs `show detailed help message` `authenticate using the given user name` `authenticate using the given password` `use a specific core in config file (default: Core)` `use alternative repository configuration file` `output the last N bytes` `output the last N lines, instead of the last 10` `sleep for approximately S seconds (default 1.0) between iterations``` `Recompile all stylesheets The recompile command will walk the entire repository and recompile all stylesheets. It is useful when changes to the underling code base require that stylesheets be reinited in the system. `show detailed help message` `authenticate using the given user name` `authenticate using the given password` `use a specific core in config file (default: Core)` `use alternative repository configuration file` The root path for the operation. Only resources within this path will get recompiled.` `Stop the 4Suite server (controller) The stop command is used to stop any or all of the 4SS servers. To stop all the servers, execute the stop command with out any arguments. To stop an individual server, specify their names as command line arguments. You will be prompted for authentication before you can stop the servers. `show detailed help message` `authenticate using the given user name` `authenticate using the given password` `use a specific core in config file (default: Core)` `use alternative repository configuration file` If specified, set the running state of this server to 'off'. This does not stop the 4ss daemon` `Start the 4Suite server (controller) The start command can be used to start any or all protocol servers. To start all of the servers, execute the start command with no paramters. To bring up individual servers, list them on the command line. `show detailed help message` `authenticate using the given user name` `authenticate using the given password` `use a specific core in config file (default: Core)` `use alternative repository configuration file` `Do not detach from the terminal` If specified, set the running state of this server to 'on'. This does not start the 4ss daemon` `Initialize the 4Suite repository Initialize the repository. This involves reformatting the storage back end (e.g. Postgres database or FlatFile root directory) and then adding the core data structures. You will LOSE ALL DATA when you execute the init, unless you use the --update option. You can only init on the machine on which the command is executed. You must have write access to where the back end stores its data (e.g., your userid must be able to write to the Postgres database if the back end is Postgres). You may be prompted for additional information to complete the init. Data Servers Dashboard `show detailed help message` `authenticate using the given user name` `authenticate using the given password` `use a specific core in config file (default: Core)` `use alternative repository configuration file` `Confirm before performing each sub-task.` `Don't destroy the current repository, just update the data.` `Only create the bare repository (destroying any current one), and don't install any components. Only useful for development.` Specify which components to add/update in the repository. Allowed values are: 'Commands' - 4ss and 4ss_manager commands and documentation; these are needed to be able to use the 4ss and 4ss_manager command-line tools; 'Docs' - All 4Suite documentation; 'Servers' - The default FtRpc and Ftp Server; 'Demos' - The default 4Suite Repository Demonstration applications and the server to access them; 'Dashboard' - The web-based control panel for 4Suite; 'Data' - Commonly used 4Suite data and icons (required; must be first component installed).` `Create a low level backup of the entire system. Create a low level system backup of the entire repository `show detailed help message` `authenticate using the given user name` `authenticate using the given password` `use a specific core in config file (default: Core)` `use alternative repository configuration file` `Exclude a path (and all children) from backup (multiple allowed)` `Directory to backup too.` `Only backup files modified since specified ISO datetime` `No extra output` `Also dump the user model` `Create an archive (not all options will work on all platforms!!) gzip'ed tar-file compressed tar file bzip2'ed tar-file ZIP file uncompressed tar file` Initial resources to start the backup at.` `Restart the 4Suite server (controller) Restart the 4Suite server (controller). `show detailed help message` `authenticate using the given user name` `authenticate using the given password` `use a specific core in config file (default: Core)` `use alternative repository configuration file``