Search
Page 69 of 107. Showing 1,065 results (0.012 seconds)
Worker Logs
The Worker outputs log information to a file called workerlog. By default, the file is located in: Linux/Mac OS X /var/log/workerlog Windows XP/2003C:\Program Files\pfx\qube\logs\workerlog Windows Vista/2008/7C:\ProgramData\pfx\qube\logs\workerlog Under L…Job logs
Logs for each job are stored in subdirectories within the logpath directory. Within each job directory, there are a number of log files associated with the job and its subjobs. The jobs are located in groups of 1000 and are created under the job_ID / 1000…Authentication Modes when in Service Mode: user and proxy
With Qube, you have a choice of running jobs as either a designated "user" or "proxy" or running jobs as one of the users with an account in the system. This is controlled with the proxy_execution_mode paramteter, which can be set to either user or proxy…Group Permissions
Qube user groups are designed to collect a set of users into a kind of partition where each user can only control other jobs owned by users in the same group. Each user in the group then can be granted permissions that only affect the jobs of other group…Common User Permission Actions
Users List users and their permissions: QubeGUI: See the Users Layout for a hierarchal list Commandline: qbusers –list Add one or more users and assign permissions: QubeGUI: In User Layout, right-click and select "Add New User" Commandline: (Use format fo…Restoring Lost Admin Privileges
Since the qbusers command has the capability of altering any user permissions, the scenario exists for an admin user to remove their own admin privileges. Should this happen, it becomes impossible to immediately restore the privileges, because the ability…First Come, First Served (FCFS)
The queue algorithm is a simple first-in, first-out system. Jobs are queued out in the order in which they are submitted. In this queuing scheme, jobs are sorted by their IDs, so jobs with lower IDs will be dispatched to run before jobs with higher IDs. I…Event names
The name is the component of the event which details when the event should take place. This is either pre-defined, or user-defined. The possible pre-defined event names for jobs are: complete Job is set to complete done Job is set to complete or killed or…Event types
The type of the event allows the system to identify the kind of event referred to. The available pre-defined names are relative to the specification of the type. The "types" of events are: job Specifies the entire job subjob Specifies a single subjob work…Editing existing SimpleCmds
It is common to edit the default values of the SimpleCmd parameters to tailor them to your site. This can be done by opening up the associated .py file under simplecmds (SimpleCmds Location) and then adjusting the default= values for the options. 1. Locat…