These instructions cover how to update existing Solaris 10 (x86) installations to new versions of EZproxy. These instructions are valid to update from any version of EZproxy to this release. This process will preserve all existing configuration files.
If you are updating from a version of EZproxy 5.0 or earlier, please be aware that the ezproxy.cfg, ezproxy.msg, and ezproxy.usr files have been renamed to config.txt, messages.txt, and user.txt in EZproxy 5.1 or later. When you perform the ./ezproxy -m step, you will be asked to allow EZproxy to rename ezproxy.cfg and ezproxy.usr to their new names. For more information on this change, including information on how to continue to use the historic names if necessary, see EZproxy 5.1 New Filenames.
- Change your current directory to the directory where EZproxy is installed with a command such as:
- Rename your existing copy of the program file ezproxy to another name such as ezproxy. yyyymmdd replacing yyyymmdd with the current year, month and day using a command such as:
mv ezproxy ezproxy. yyyymmdd
- Download ezproxy-sol10-x86.bin into the directory where EZproxy is installed. If you download this file on different system and use FTP to move it to your EZproxy server, be sure to perform this transfer using binary.
- Rename the program and make it executable with the commands:
mv ezproxy-sol10-x86.bin ezproxy
chmod 755 ezproxy
- During this step, if you are updating from EZproxy 5.0 or earlier, you will be asked to allow ezproxy.cfg to be renamed to config.txt and to allow ezproxy.usr to be renamed to user.txt. See EZproxy 5.1 New Filenames for more information.
Create any new files required for the updated release with the command:
- Use the following command to stop the old version of EZproxy:
- This step is optional. If you are updating from a EZproxy 5.0 or earlier, you can choose to rename your existing ezproxy.msg to messages.txt, or you can leave the existing file alone and EZproxy will create a new messages.txt file.
If you would like to rename the existing file, issue the command:
mv ezproxy.msg messages.txt
- Start EZproxy with the command: