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.
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.
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.
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
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 |
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.
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. |
/var/sysman/supper scan power_system
This builds a new scan file for the collection.
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.
/var/sysman/supper update power_system
/var/sysman/supper update node.root