Managing the AMASS File System
Step |
| Command | Description |
|
|
| |
1 | Log in as amass or root. |
| |
|
|
| |
2 | sysperf [updateinterval] | To make sure there are no | |
|
|
| pending write requests in |
|
|
| the AMASS queue, view |
|
|
| the queue with the |
|
|
| sysperf command. Log in |
|
|
| as root and enter the |
|
|
| command as shown in the |
|
|
| following steps. To stop the |
|
|
| sysperf command, use |
|
|
| |
|
|
| Run only one sysperf |
|
|
| command at a time. |
|
|
|
|
3 | cd | /usr/amass/tools | Disable AMASS at system |
|
| ./amass_atboot | startup. |
|
|
| |
4 | Reboot the UNIX server and AMASS will not automatically | ||
| start. |
|
|
|
|
|
|
5 | cd | /usr/amass/scripts | Rerun the installamass |
|
| ./installamass | script and make the |
|
|
| necessary configuration |
|
|
| changes. |
|
|
| |
6 | Reboot the system for the changes to take effect. | ||
|
|
| |
7 | <AMASS_W_9031>: AMASS | If you change any of the | |
| configuration has been | AMASS | |
| changed...checkpoint | configuration parameters, | |
| area is invalid | this error message may | |
|
|
| appear after AMASS |
|
|
| restarts. Under these |
|
|
| circumstances, this |
|
|
| message can be ignored |
|
|
|
|
Operational Tasks |