BigFix Technical Search
Search BigFix
|
|
|
| Search Areas | |||
| BigFix Support Website | Knowledge Base | ||
| User Forums | Main BigFix Website | ||
Looking for info on the BigFix Relevance Language? Try the Inspector Search Engine. |
|||
Summary:
How do I manually run the download cacher tool for SuSE Linux Enterprise?
Solution:
The download cacher tool for SuSE Linux Enterprise is a Perl executable designed to automatically download and cache SuSE RPM packages to facilitate deployment of SuSE Linux Enterprise Fixlet messages.
The tool can be downloaded from the BES Support website here.
To run this tool, you may wish to create a batch file with the following parameters. If you run the tool without specifying any parameters, you will be prompted to enter the parameters at the command line.
Sample.bat
SUSEDownloadCacher.exe novell_username novell_password cache C:\logs yes patch-11001 I386 9 PROXY http://www.proxyserver.com:8080 proxy_user proxy_password
Usage -
SUSEDownloadCacher.exe NovellUsername NovellPassword DirectoryPath/cache [Logfile Directory] [Increase Cache] [SuSE Architecture(s)] [Patch ID(s)] [SuSE OS Version(s)] [--no-rename] [PROXY] [Proxy URL] [Proxy Username] [Proxy Password]
Required Parameters:
NovellUsername
Your Novell Account Username (used to log into http://support.novell.com/linux/psdb/)
NovellPassword
Your Novell Account Password (used to log into http://support.novell.com/linux/psdb/)
DirectoryPath/cache
The full path to the folder in which you would save downloaded files. The keyword 'cache' indicates that files would be downloaded to the BES Server cache and should only be used when SUSEDownloadCache.exe is run on a BES Server machine.
Optional Parameters:
[Logfile Directory]
Full path to the folder where you would like to create the log file. By default, the logfile is placed in the BES Client Logs directory (ex: C:\Program Files\BigFix Enterprise\BES Client\__BESData\__Global\Logs)
[Increase Cache]
This option is only available if the specified Directory Path is the keyword 'cache'. Enter 'yes' to increase the BES Server cache automatically in the event that the size of the files being downloaded exceeds the current amount of free space in the cache. Enter 'no' or leave blank to be prompted to manually increase the cache.
[Architecture(s)]
BigFix currently supports SuSE Linux Enterprise I386 and X86_64 architectures. Enter a space-delimited list (e.g. "I386", "I386 x86_64") to indicate the architecture(s) for which you would like to download files. If you do not specify this parameter, the tool will cache downloads for both architecture(s).
[Patch ID(s)]
Specify SuSE Patch ID. Separate each patch-ID with a space (ex: patch-11001 patch-B6121109 patch-11055). Use this option when you wish to download files for specific patch. If you do not specify this parameter, the tool will cache all files for all published Fixlet messages in the SuSE Linux EnterpriseFixlet site. You can read more about the BigFix ID scheme for SUSE Linux Enterprise patches here.
[SuSE OS Version(s)]
BigFix currently supports SuSE Linux Enterprise 9.0 and 10.0. Enter a space-delimited list (e.g. "9", "9 10") to indicate the version(s) for which you would like to download files. If you do not specify this parameter, the tool will cache downloads for all versions.
[PROXY] [Proxy URL] [Proxy Username] [Proxy Password]
'PROXY' is a keyword used to indicate that downloads must go through a proxy server. If your network requires a proxy server for Internet access, you must specify this keyword and provide required parameters.
Proxy URL is the URL of your proxy server. This is usually the ip address or dns name of your proxy server, and its port, separated by a colon (ex: http://192.168.100.10:8080).
If your proxy server requires authentication, you must specify your Proxy Username and Proxy Password. Your Proxy Username is usually in the form of domain\username.
[--no-rename]
Use this option when you do NOT want to rename the downloaded rpm files to their corresponding sha1s .
--email [Internal SMTP Server] [login] [password] [sender@email.com][receiver1@email.com;receiver2@email.com]: Use this option to send a notification email containing a summary of the execution of the download cacher.
- [Internal SMTP Server]: specify which email server you would like to use to send the notification
- [login]: username for the email server, or "none" if no login is required
- [password]: password for the email server, or "none" if no password is required
- [sender@email.com]: the summary will be sent from this address
- [receiver1@email.com;receiver2@email.com;...]: specify as many recipients as are necessary, separated by semicolons
[RPM filenames]: specify the full filename of the package(s) you wish to download, separated by a space. (e.g. "psstack-1.2-3.EL.2.i386.rpm firefox-1.5-3.x86_64.rpm").
[MIRROR9 / MIRROR10] [mirroraddress]: Use this option to download files from a Novell mirror. If using this option, replace the NovellUser and NovellPassword credentials with your mirror credentials.
[MIRROR9 / MIRROR10]: specify MIRROR9 if you wish to use a Suse 9 mirror. Specify MIRROR10 if you wish to use a Suse 10 mirror.
[mirroraddress]: specify the root address of the Suse mirror. If you wish to use a local mirror, it must follow the same folder structure as Novell's online mirror. (e.g. If Novell's online mirror has the form https://nu.novell.com/repo/$RCE/SLES10-SP2-Updates/sles-10-i586/rpm/, then your local mirror must be of the form http://local.mirror.com/repo/$RCE/SLES10-SP2-Updates/sles-10-i586/rpm/ -- in this case you would specify either "https://nu.novell.com" or "http://local.mirror.com" as the mirror address)
Sample Usage:
SUSEDownloadCacher.exe suse_user suse_password cache C:\logs yes patch-12383 x86 x86_64 --email mailer.email.com none none sender@email.com receiver@email.com
SUSEDownloadCacher.exe --rpm-names redhat_user redhat_password cache C:\logs psstack-1.2.3.EL.2.i386.rpm firefox-1.5-3.x86_64.rpm
Caveat:
The Download Cacher Tool may not download all rpm files successfully from the Novell server. Running the tool at a later time can sometimes resolve this issue. Failed downloads can also be manually downloaded. To view a summary of successful and failed downloads, view the SUSEDownload.log.
Knowledge Base ID: | 363 |
Version Information: | |
Creation Date: | 25 Jul 2006 18:29:48 |
Last Modified Date: | 1 Jul 2009 02:18:32 |