Versions Compared

    Old Version 4

    changes.mady.by.user Unknown User (czerouni)

    Saved on

    compared with

    New Version Current

    changes.mady.by.user John Burk

    Saved on

    Key

    • This line was added.
    • This line was removed.
    • Formatting was changed.
    Comment: Published by Scroll Versions from this space and version 6.9-0

    ...

    There are two required files (and one a third optional onefile) that control the Qube! supervisor:

    ...

    qb.lic
    The qb.lic file must contain a license key string issued by PipelineFX. Additional key strings can be added to the file in no particular order. Whenever adding a new key to the file, always make a backup copy first. Licenses can be added through the WranglerView UI - see Installing Qube! Licenses.

    qbwrk.conf (optional)
    The qbwrk.conf file is an optional file on the Supervisor that centrally configures all of the Qube! Workers under the Supervisor. See the section on "Centrally Configuring Workers" Centralized Worker Configuration for more information.

    File Locations

    These files are located in the following directories depending on the platform:

    • Linux & OS X:             /etc
    • Windows XP/2003:     C:\WindowsWindows Vista/2008:  C:\ProgramData\pfx\qube
    • Windows XP/2003:     C:\Windows

    The Current Configuration

    You can discover the current Supervisor configuration by reading the qb.conf file directly, or by issuing this qbadmin command

    $ qbadmin supervisor --configuration

    or by using the WranglerView UI Administration menu item, shown here

    Image Added

    Modifying the Files

    You can modify the qb.conf and/or and qbwrk.conf conf files from the WranglerView UI in the Administration menu item, or by directly modifying the files with a text editor. If you use the UI, you must run it as root or a user with Admin capabilities, and you must run it on the actual Supervisor. Making Supervisor changes from a Worker acts like it is doing something, but it actually has no effect.

    Once changes have been made to the Supervisor configuration, it must be made aware of configuration changes by restarting the Supervisor service (but not all changes will require a restart - for some you can tell the Supervisor to simply reload the qb.conf file). If you are modifying through WranglerView, it should automatically prompt the user to restart the Supervisor. The Administration menu in WranglerView can also be used to manually explicitly restart the Qube! Supervisor. You can also force the Supervisor to reload the qb.conf file with this command

    ...