GUI Reference: Analysis Cloud; Launchd Group

• Navigating To
• Page Properties
• Analysis Cloud vs Launchd Group Page
• Contents and Usage
• Operations on Child Elements
• Launchd Group Outline
• Navigating from
• Related Tasks

Important Note: the CodeSonar Web GUI makes extensive use of JavaScript. Make sure JavaScript is enabled in your web browser.

Navigating To

Page Properties

Analysis Cloud vs Launchd Group Page

The Analysis Cloud page and Launchd Group pages have very similar contents and functionality, so are documented together. The differences between the two are summarized in the following table.

Contents and Usage

The following annotated screenshot shows the various parts of the Analysis Cloud and Launchd Group pages.

Standard Header

See GUI Reference: Standard Header.

Breadcrumbs

Page Heading

Summary Information and Create Functionality

Two sections, both hidden by default: Details and Create New Launchd Group.

Launchd Group Details

Click for general information about the launchd group. Launchd Group The launchd group name. To change the name, click edit and enter a new name, then click Save. Launchd group names must be unique. The name of the root launchd group cannot be modified. To remove this launchd group from the hub, click remove this launchd group then confirm when prompted. Note that this will remove all launchd groups and launch daemons in the subhierarchy under this launchd group. To view or modify the role-permissions for the launchd group, click permissions or to navigate to the Launchd Group Role-Permissions page. The root launchd group cannot be renamed or deleted, so does not offer edit or remove this launchd group links. Parent Path The launchd group's ancestors, as a /-separated sequence of launchd group names with a leading / representing the root launchd group. To move the launchd group to a different location in the hub's launchd group hierarchy, click edit and enter the path to the parent launchd group that you wish to move to, then click Save. The root launchd group has no parent and cannot be moved, so the Analysis Cloud page (and Launchd Group page for the root launchd group) does not include this element. Description To change the description, click edit and enter a new description, then click Save. Created   (Not available on Analysis Cloud page for users without LAUNCHDGROUP_READ permission for the root launchd group.)

Create New Launchd Group

Use this link to create a new, empty launchd group as a child of the current launchd group: enter the new name in the text field, then click Create. Launchd group names must be unique. This is the only location that provides functionality for creating a new launchd group. (Not available on Analysis Cloud page for users without LAUNCHDGROUP_READ permission for the root launchd group.)

Link to Analysis Cloud Active Jobs Page

Click View breakdown by machine and active analysis to navigate to the hub Analysis Cloud Active Jobs page.

Table of launch daemons and launchd groups

A table describing the launch daemons and launchd groups that are children of the current launchd group.
On the Analysis Cloud page, the table also includes launch daemons and launchd groups whose parent launchd group is some group for which the user does not have LAUNCHDGROUP_EXISTS permission.

• The table has the standard pagination controls.
• Click on any launchd group entry in the table to navigate the corresponding Launchd Group page.
  (Launch daemons do not have their own information pages.)
• The available table columns are as follows. Columns displayed by default are marked with an asterisk (*).

  Column Label	Column Data
  	Launch Daemon Entry	Launchd Group Entry
  none
  ID	Launch Daemon.Launch Daemon ID	Launchd Group.LDGroup ID
  Name *	Launch Daemon.Launch Daemon.Derived Name	Launchd Group.LDGroup Name
  Machine *	Launch Daemon.Machine	-
  Installation Path *	Launch Daemon.Installation	-
  User *	Launch Daemon.System User	-
  Hub User *	Launch Daemon.Hub User	-
  Path	Launch Daemon.LDPath	Launchd Group.LDGroup Path
  Max Processes *	Launch Daemon.Process Limit You can use this page to change the process limits for launch daemons for which you have LAUNCHD_WRITE permission. To change the process limit for a single launch daemon: Enter the new limit in the Max Processes field. Set to the empty string to specify that the launch daemon should perform automatic load balancing. The table will expand to display Save and Cancel buttons. Click Save. Only signed-in users can save changes to the hub: if you are not already signed in when you click Save, CodeSonar will ask you to Sign In before saving your change. To change multiple process limits at once, use the Change Multiple button.	-
  Running Processes *	The number of current processes for the launch daemon.	-
  Status *	Launch Daemon.Status	-
  Address	Launch Daemon.Address	-
  Protocol Version	Launch Daemon.Protocol Version	-
  Key	Launch Daemon.Key	-
  Space Quota	Launch Daemon.Space Quota (in MB)	-
  Space Used	Launch Daemon.Space Used (in MB)	-
  Disk Space Available	The amount of free space (in MB) on the disk that contains the Home Directory.	-
  Home	Launch Daemon.Home Directory	-
  * ("Permissions Link")	Click to navigate to the corresponding Launch Daemon Role-Permissions page.	Click to navigate to the corresponding Launchd Group Role-Permissions page.

Change/Move/Remove Multiple buttons

There are three buttons under the table, providing various operations on the launch daemons and launchd groups in the table.

For more information, see Operations on Child Launch Daemons and Launchd Groups, below.

Standard Footer

See GUI Reference: Standard Footer.

Operations on Child Launch Daemons and Launchd Groups

The Analysis Cloud and Launchd Group pages provide several operations on the launch daemons and launchd groups in the table.

• Change max processes for multiple launch daemons.
• Move one or more launch daemons/launchd groups to a different parent launchd group.
• Delete one or more launch daemons/launchd groups from the hub.

Change max processes for multiple launch daemons

Follow these steps to set the process limit for multiple launch daemons at once.

1. Click the Change Multiple button under the table of launch daemons and launchd groups. The page will expand to provide more functionality, as shown below.
   

   Table rows	The table will contents will update to show only those launch daemons for which you have LAUNCHD_WRITE permission.
   Checkboxes	The table now includes a column of checkboxes. Click in a checkbox to select the corresponding launch daemon, click again to deselect.
   Check/Uncheck Buttons	Check All Click to select all launch daemons in the table (including those on other pages of a paged table). Uncheck All Click to unselect all launch daemons in the table (including those on other pages of a paged table). Check These N Click to select all launch daemons on the current page of the table. The number N corresponds to the number of launch daemons on the current page. (Only present if table has multiple pages.) Uncheck These N Click to unselect all launch daemons on the current page of the table. The number N corresponds to the number of launch daemons on the current page. (Only present if table has multiple pages.)

2. Use the checkboxes to select the launch daemons that you want to modify.
3. Enter the new process limit for your selected launch daemons in the Max Processes field, then click Save Changes.

   CodeSonar will update the analysis cloud register entries for the selected launch daemons, then reload the page to show the updated information along with a confirmation message.

Move one or more launch daemons/launchd groups to a different parent launchd group

From time to time, you may wish to change the organization of the launchd group/launch daemon hierarchy and move launchd groups and launch daemons around by changing their parent launchd groups, as described here.

1. Before you can move the launch daemons and launchd groups, you will need to decide on a destination: a launchd group G that will become the parent launchd group for those launch daemons and launchd groups.
   • G must already exist on the hub (you cannot implicitly create a launchd group by specifying it as a parent).
   • You must have LAUNCHDGROUP_EXISTS G and LAUNCHDGROUP_ADD_CHILD G permissions.

   As part of the move procedure, you will specify the path to the destination launchd group. This must be the full LDGroup Path: a /-separated sequence of LDGroup Name, with a leading / representing the root launchd group.
   For example:

   /	The root launchd group.
   /GroupA	A launchd group named GroupA, whose own parent is the root launchd group.
   /GroupA/SubgroupB	A launchd groupnamed SubgroupB, whose parent is GroupA; the parent of GroupA is the root launchd group.

2. Click the Move Multiple button under the table of launch daemons and launchd groups.
   The page will expand to provide more functionality. This expansion is very similar to that for Change Multiple: the differences are as follows.
   • The table contents update to include only:
     • launchd groups for which you have LAUNCHDGROUP_WRITE permission, and
     • launch daemons for which you have LAUNCHD_WRITE permission.
   • There is a New Parent Path text field (rather than a "Max Processes" field).
   • The confirmation button is labeled Move Selected Launch Daemons (rather than "Save Changes").
3. Use the checkboxes to select the launchd groups and launch daemons that you wish to move.
4. Enter the path to the new parent launchd group in the New Parent Path field.
5. Click the Move Selected Launch Daemons button.

   If there are multiple launchd groups that match the specified path and for which you have LAUNCHDGROUP_EXISTS permission, CodeSonar will display a table of the matching launchd groups and ask you to select one.
   (Otherwise, the move will take place without this step.)

   1. Click the Use This One button corresponding to the launchd group that you wish to set as the new parent.

   CodeSonar will print progress messages as it moves the launch daemons and launchd groups. When it has finished, there will be a confirmation message for each item that has been moved, along with a Continue link.

6. Click Continue to return to the Analysis Cloud or Launchd Group page.

Delete one or more launch daemons/launchd groups from the hub

Deleting a launch daemon D from the hub removes all the information associated with D from the hub's analysis cloud register. Similarly, deleting a launchd group G will recursively delete all the launchd groups and launch daemons for which G is an ancestor, as well as deleting all information about G.

You will only be able to delete elements for which you have sufficient deletion permissions:

The procedure for deleting one or more launchd groups or launch daemons is as follows.

1. Click the Remove Multiple button under the table of launch daemons and launchd groups.
   The page will expand to provide more functionality. This expansion is very similar to that for Change Multiple: the differences are as follows.
   • The table contents update to include only:
     • launchd groups for which you have LAUNCHDGROUP_DELETE permission, and
     • launch daemons for which you have LAUNCHD_DELETE permission.
     Note that these are only a subset of the permissions required for deletion: the full set of permissions will be checked before each deletion takes place.
   • There is no text field.
   • The confirmation button is labeled Remove Selected Launch Daemons (rather than "Save Changes").
2. Use the checkboxes to select the launchd groups and launch daemons that you want to remove.
3. Click the Remove Selected Launch Daemons button to remove the launchd groups and launch daemons you have selected.

   CodeSonar will print progress messages as it removes the launchd groups and launch daemons. When it has finished, there will be a confirmation message for each item that has been removed, along with a Continue link.

4. Click Continue to return to the Analysis Cloud or Launchd Group page.

Launchd Group Outline

The Launchd Group Outline provides an overview of the hub's launchd group hierarchy for orientation and navigation.

In its collapsed state, the Launchd Group Outline is indicated by a shaded bar at the left of the Analysis Cloud page and all Launchd Group pages. It is expanded by default if it has contents other than the root launchd group.

The outline includes all launchd groups on the hub for which the user has LAUNCHDGROUP_EXISTS permission, along with all ancestors of such groups (regardless of the ancestor permissions). The outline is always ordered so that the launchd group path to the current launchd group is at the top of the display, and the current launchd group is highlighted.

• Click any launchd group name to navigate to the corresponding Launchd Group page.
• Click [+] next to a launchd group name to expand the subtree under that launchd group; click [-] to collapse the subtree again.
• Click >>>more at the bottom of a subtree listing to display the remainder of that subtree.

Expanding, Resizing, and Collapsing

The launchd group outline is analogous to the Project Tree Outline provided on Home and Project Tree pages: it operates on the launchd group hierarchy, while the project tree outline operates on the project tree hierarchy. In particular, you may want to look at the project tree outline example: two users with different sets of LAUNCHDGROUP_EXISTS permissions will similarly see different Launchd Group Outline contents.

Navigating from

Related Tasks

• Distribute analysis work over specific machines