Bug 509656
| Summary: | RFE: mail notifications should be directed to operator | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Vadym Chepkov <vchepkov> |
| Component: | apcupsd | Assignee: | Michal Hlavinka <mhlavink> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 11 | CC: | mhlavink |
| 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: | 2009-11-25 11:23:47 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
Vadym Chepkov
2009-07-04 16:59:13 UTC
This is not a bug, but a feature request and it's not variable set during package build, so I need to convince upstream for this. I wasn't able to find any documentation and/or recommendation for operator role usage. Do you know about some material/link I can use for convincing upstream? I was looking for "feature request" switch in bugzilla, but didn't see it, I apologize if I missed it. as for 'operator' documentation, I don't think there is any, except this user id is defined in Linux Standard Base and it seems most suitable. (http://refspecs.linux-foundation.org/LSB_3.2.0/LSB-Core-generic/LSB-Core-generic/usernames.html) root is widely abused and this particular case is one of them. If "Change battery" notification arrives root either have to forward this e-mail to a responsible person or it has to modify all scripts in /etc/apcupsd/ right away, instead of just modifying entry in/etc/aliases. When you are filling feature request next time use "RFE: " as prefix in summary field. If it is complex feature request requiring more time/work, also add FutureFeature keyword to Keywords field and use rawhide as version. I'll try to convince upstream, but I don't know if I'll be successful. We'll see. well... I've pinged them twice, but still got no answer yet... maybe it'll take some time I did not succeed convincing upstream to make these changes and I don't think this is such important to maintain separate patches. If this is important for you, you can try to convince upstream. |