Bug 183405
Summary: | rhnpush config files don't behave in the standard way | ||
---|---|---|---|
Product: | [Retired] Red Hat Network | Reporter: | John Wregglesworth <wregglej> |
Component: | RHN/Backend | Assignee: | Todd Sanders <tsanders> |
Status: | CLOSED WONTFIX | QA Contact: | Red Hat Satellite QA List <satqe-list> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rhn410 | CC: | acarter, rhn-bugs |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-10-15 15:37:19 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
John Wregglesworth
2006-02-28 21:31:52 UTC
John, not certain I understand the bug. If it's just complaining that the defaults aren't in the file, but it then does what it needs to do based on internal defaults, that's actually a GoodThing(tm) in my opinion. It does 2 main things: 1) it gives people an understanding of the universe of configuration options 2) it tells them what the default value is. I.e., they don't have to trace through the source to find the hard-coded defaults Let's talk about this some more so I understand what you feel is busted here, but for now, I'm going to move it to rhn-uncommited. User wregglej's account has been closed This bug has been closed due to inactivity. Please open a new bug with specific details if this problem is still occurring or if an enhancement is needed. |