Red Hat Bugzilla – Bug 1480810
rhn.conf man page does not contain the taskomatic initial memory option
Last modified: 2018-03-06 10:46:27 EST
I have created a commit upstream to change the Taskomatic maxmemory variable in the rhn.conf man page from "taskomatic.maxmemory" to "taskomatic.java.maxmemory" and added documentation for "taskomatic.java.initmemory".
Candace, can you please look at my comments I've made to pull request at https://github.com/spacewalkproject/spacewalk/pull/565/files ?
I replied on the PR. Let me know what you think :) Thank you!
PR merged into spacewalk.git(master): adcaa71a9a90fd101373020e652b98ecdcd1c2e5
Verified on spacewalk-config-2.6.0-4. Compared to spacewalk-config-2.6.0-4, following item were added to the rhn.conf man page:
The maximum amount of memory (MB) that Taskomatic can use. If you find that Taskomatic is running out of memory, consider increasing this.
The initial amount of memory (MB) that Taskomatic is allocated on start-up.
When importing packages, skip non-essential data that can make the import faster (changelogs). Not recommended in production.
"taskomatic.maxmemory" option is gone. Default values are consistent with settings in /usr/share/rhn/config-defaults/rhn_taskomatic_daemon.conf
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.