[Bug 977051] New: Yum section should document using a proxy
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=977051
Bug ID: 977051
Summary: Yum section should document using a proxy
Product: Fedora Documentation
Version: devel
Component: system-administrator's-guide
Severity: unspecified
Priority: unspecified
Assignee: jhradile(a)redhat.com
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jhradile(a)redhat.com
Using yum behind a proxy requires special configuration, and the guide does not
document this relatively common support question. I think some instructions
should be added for this, either as a term in the yum [main] section or an
independent section.
--
You are receiving this mail because:
You are the QA Contact for the bug.
10 years, 10 months
[Bug 922608] New: Setting up named-chroot using setup-named-chroot not documented
by Red Hat Bugzilla
Product: Fedora Documentation
https://bugzilla.redhat.com/show_bug.cgi?id=922608
Bug ID: 922608
Summary: Setting up named-chroot using setup-named-chroot not
documented
Product: Fedora Documentation
Version: devel
Component: deployment-guide
Severity: high
Priority: unspecified
Assignee: jhradile(a)redhat.com
Reporter: harker-redhat(a)harker.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: dhensley(a)redhat.com, oglesbyzm(a)gmail.com
Description of problem:
In FC18 completely changed you configure the named-chroot package.
In RHEL when you install the named-chroot package, the /var/named/chroot
environment gets setup automatically.
In FC18 installing named-chroot package does not set up the /var/named/chroot
environment.
In FC18 you need to initialize the /var/named/chroot environment by running:
/usr/libexec/setup-named-chroot.sh /var/named/chroot on
I suspect this change was made with the transition to systemd.
Version-Release number of selected component (if applicable):
bind-chroot.x86_64 32:9.9.2-8.P1.fc18
How reproducible:
www.google.com/search?q=setup-named-chroot&as_sitesearch=fedoraproject.org
Steps to Reproduce:
Search:
www.google.com/search?q=setup-named-chroot&as_sitesearch=fedoraproject.org
Actual results:
No results
Expected results:
Some documentation
Additional info:
Here are a set of steps I wrote about setting named-chroot in FC18:
# Steps to set up a named in a chroot environment in FC18
# Install the packages
yum install bind bind-chroot
# Enable chroot environment
# Note: This is a significant change (in FC18)/(relating to systemd)
/usr/libexec/setup-named-chroot.sh /var/named/chroot on
# Check chroot environment
ls -l /var/named/chroot/etc /var/named/chroot/var/named
# Optional:
# You may also want to hard link named.conf and rndc.key from
/var/named/chroot/etc to /etc.
# Check with
ls -li /etc/named.conf /var/named/chroot/etc/named.conf
ls -li /etc/rndc.key /var/named/chroot/etc/rndc.key
# Create hard links with (ln with no -s)
ln /var/named/chroot/etc/named.conf /etc/named.conf
ln /var/named/chroot/etc/rndc.key /etc/rndc.key
# Enable the named-chroot service
# Note: If you are running named-chroot.service you do not run named.service
# Note: This is a significant change (in FC18)/(relating to systemd)
systemctl enable named-chroot.service
systemctl start named-chroot.service
# Check with
systemctl status named-chroot.service
# For ease in named administration add yourself to group named
useradd ???
Note: FC18 still uses the rndc command to manage named. Systemd only
start/stops the named daemon
--
You are receiving this mail because:
You are the QA Contact for the bug.
10 years, 10 months
[Bug 607270] Repo Query
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=607270
Pete Travis <me(a)petetravis.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|software-management-guide |system-administrator's-guid
| |e
Assignee|nobody(a)fedoraproject.org |jhradile(a)redhat.com
QA Contact|jsmith.fedora(a)gmail.com |docs-qa(a)lists.fedoraproject
| |.org
--- Comment #4 from Pete Travis <me(a)petetravis.com> ---
Thanks Jaromir, reassigning.
--
You are receiving this mail because:
You are the QA Contact for the bug.
10 years, 10 months
[Bug 929426] firewalld: forward chain
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=929426
Pete Travis <me(a)petetravis.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |me(a)petetravis.com,
| |oglesbyzm(a)gmail.com,
| |pkennedy(a)redhat.com,
| |security-guide-list@redhat.
| |com, sparks(a)redhat.com
Component|fedora-websites |security-guide
Assignee|web-members(a)fedoraproject.o |sparks(a)redhat.com
|rg |
QA Contact|web-members(a)fedoraproject.o |docs-qa(a)lists.fedoraproject
|rg |.org
--- Comment #2 from Pete Travis <me(a)petetravis.com> ---
Reassigning to the Security Guide component, firewalld will be covered there.
--
You are receiving this mail because:
You are the QA Contact for the bug.
10 years, 10 months
[Bug 970772] New: Wake On Lan Fails for Intel E100 with > kernel-3.5.7
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=970772
Bug ID: 970772
Summary: Wake On Lan Fails for Intel E100 with > kernel-3.5.7
Product: Fedora Documentation
Version: devel
Component: about-fedora
Severity: unspecified
Priority: unspecified
Assignee: stickster(a)gmail.com
Reporter: rogerx.oss(a)gmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: oglesbyzm(a)gmail.com, stickster(a)gmail.com
Description of problem: Sometime after kernel-3.5.7, Wake On Lan functionality
with Intel e100 PCI cards no longer functions.
Upstream Bug report filed here:
https://bugzilla.kernel.org/show_bug.cgi?id=56181
This apparently affects all Intel E100 PCI based Network Cards, or those
dependant on the e100 kernel module.
(Might want to add this as a blocker before stabalizing or removing stable
kernels.)
--
You are receiving this mail because:
You are the QA Contact for the bug.
10 years, 11 months