Radiator Frequently Asked Questions

Do you accept patches for Radiator

Yes, we are always happy to receive and evaluate patches, fixes, enhancements and suggestions. For your protection and ours, you must first provide a Contributor License Agreement Then you can send code, documentation or ideas by email to any of the product mailing lists, or by private email to info@radiatorsoftware.com. We evaluate them and possibly include them in the base product according to the following criteria:

  1. General usefulness for a significant number of users
  2. Backwards compatibility
  3. Impact on performance
  4. Ease of understanding and configuration for administrators.

Unfortunately, not all patches will meet these criteria, and so not all will be included into the base product. If we decide not to include a patch in the base product, we will often put it in the goodies directory of the distribution for use by others.

How do I make my own RPMs?

The Radiator RPM distributions are easy to install many types of on Linux. However Radiator Software does not make patch sets available for RPM distributions, only for the full source distribution. Further, some customers may need RPMs of customised versions of Radiator. On most linux platforms that support RPMs you can make you own RPMs from the Radiator source to suit your own needs.

  • Download the full source file and the patches file from the Radiator downloads page to a working directory
  • tar zxvf Radiator-4.7.tgz
  • cd Radiator-4.7
  • tar zxvf ../patches-4.7.tar.gz
  • perl Makefile.pl (you could do ‘make install’ here, and avoid the need to make an RPM)
  • make dist
  • su make rpm
Where does the RPM install the doc and goodies?
The RPM package installs these by default in /usr/share/doc/packages/Radiator/
Radiator cant connect to RSAAM ?
In some circumstances, The Radiator connection to RSA AM may fail with an error message in the RSA Weblogic server like: Received fatal alert: bad_record_mac at sun.reflect.NativeConstructorAccessorImpl.newInstance0  This can be fixed by adding these lines to the weblog server start file: -Dhttps.protocols=SSLv3,TLSv1 -Dsun.security.ssl.allowLegacyHelloMessages=true -Dsun.security.ssl.allowUnsafeRenegotiation=true
I’m having problems using IPv6
IPv6 should work automatically with recent Perl installations. Socket6.pm Perl module may be required with older Perls. If you are using ActivePerl, try installing Socket6 PPM to see if this fixes the problem.