Administration Guide

Adding and deleting files in a file collection

Adding and deleting files in a file collection are a bit more complicated than adding and deleting files in a standard directory. The prefix, list, and refuse master files contain criteria that define which files are in a particular collection. The master files are read and processed by the scan, install, and update commands. When you add or delete files in a file collection, you need to review the contents of these master files. For more information about the master files and how they work, see Building a file collection.

The examples in this section show how to add the /etc/environment file to the node.root collection.

Step 1: Add or delete files in the file system

Be sure you are working with the master files.
The same considerations you make to update files also apply here. Verify that you are on the machine that is the master server for the collection you are changing. See Understanding how file collections are organized to review file collection hierarchy.
Add or delete files in the file system using standard AIX file commands.
When adding files, you need to consider whether the files are in a primary or secondary collection, what the prefix and list files in that collection contain, and the position of the new files in the file tree. Remember, the supper commands begin their search starting at the point defined in the prefix file. For any file collection on an SP host, this is the root (/) directory. All files encountered that pass the criteria defined in the list file are considered part of the file collection.

Examples

To add a file to the node.root collection which is a secondary collection under the power_system collection, you would copy the file to the /share/power/system/3.2 directory. The /var/sysman/sup/node.root/prefix file shows that the directory search for this collection begins at /share/power/system/3.2. The /var/sysman/sup/node.root/list for this example contains the following:
```
   symlinkall
   omit    ./usr
   upgrade .
```
The entry upgrade . indicates that all files encountered in the /share/power/system/3.2 directory during the search are to be upgraded.
To add /etc/environment in our default configuration, log in to the control workstation and copy /etc/environment to the /share/power/system/3.2 directory:
```
   cp /etc/environment /share/power/system/3.2/etc/environment
```
To add a file to the user.admin collection, you would proceed differently. The /var/sysman/sup/user.admin/prefix file shows that the directory search starts at the root of the file tree, therefore, the directory search would find the /etc/environment file. The /var/sysman/sup/user.admin/list file shows that only those files specifically listed will be upgraded instead of the entire directory.
In this case, you do not need to copy the file. Instead, add a specific entry to the list file to upgrade it.

Note
To add a file to a collection, the file must permit others to have read access. To delete a file from a file collection, either remove it on the master server or delete its entry in the list file and proceed with the other steps in this task. For example, to remove /etc/environment from the node.root collection, log in to the control workstation and enter: rm /share/power/system/3.2/etc/environment

Note

To add a file to a collection, the file must permit others to have read access.

To delete a file from a file collection, either remove it on the master server or delete its entry in the list file and proceed with the other steps in this task.

For example, to remove /etc/environment from the node.root collection, log in to the control workstation and enter:

   rm /share/power/system/3.2/etc/environment

Step 2: Run the supper scan command (optional)

The scan is not a required file and not all file collections have one. Check the file collection directory to see if the collection you are updating has a scan file.

If you have a scan file in this collection and you want to maintain it, you must run the supper scan command on the master collection every time you make a change. When a scan file is present, the update command reads it as an inventory of the files in the collection and does not do the directory search.
You also have the option of deleting the scan file and allowing supper to process the file collection without it.
Note

If you keep the scan file and fail to run the supper scan command when you add files, the scan file will not be current and the new files will not be included in the collection.
If you do not have a scan file in this collection, the update command will search the directory, apply the criteria in the master files, and add the new file.

Note
If you keep the scan file and fail to run the supper scan command when you add files, the scan file will not be current and the new files will not be included in the collection.

Example

Run the supper scan command on the control workstation:
```
   /var/sysman/supper scan power_system
```
This builds a new scan file for the collection.
Check the scan file to verify that it contains the additional /etc/environment file.

Step 3: Run the supper update command

Run the supper update command everywhere you want this change to be effective. See Step 3: Run the supper update command for your options in performing this step.

Example

Log in to each server requiring the new file. The /etc/environment file is in the node.root collection as a secondary collection available within the power_system collection. Enter:
```
   /var/sysman/supper update power_system
```
Log in to each of the nodes requiring the new file. On the nodes you update the node.root collection. Enter:
```
   /var/sysman/supper update node.root
```
Check the supper messages to verify the updates worked.

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]