Bug 358911 – installation of bind-chroot causes problems with df

Bug 358911 - installation of bind-chroot causes problems with df

Summary:	installation of bind-chroot causes problems with df

Status:	CLOSED DUPLICATE of bug 202441

Aliases:	None

Product:	Red Hat Enterprise Linux 4
Classification:	Red Hat
Component:	bind (Show other bugs)
Sub Component:
Version:	4.4
Hardware:	All Linux

Priority	low Severity low
Target Milestone:	---
Target Release:	---
Assigned To:	Adam Tkac
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2007-10-30 15:13 EDT by Joseph Shraibman
Modified:	2013-04-30 19:37 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2007-10-31 06:09:00 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Joseph Shraibman 2007-10-30 15:13:05 EDT

Description of problem:
After installing bind-chroot, df prints this whenever it is run a a non-superuser:
df: `/var/named/chroot/proc': Permission denied

Version-Release number of selected component (if applicable):
coreutils-5.2.1-31.6
bind-chroot-9.2.4-27.0.1.el4

How reproducible:
All the time

Steps to Reproduce:
1. install bind-chroot
2. As a user other than root run 'df'
3.
  
Actual results:
df: `/var/named/chroot/proc': Permission denied

Comment 1 Joseph Shraibman 2007-10-30 15:49:03 EDT

Fixing this problem is as simple as doing "chmod a+rx /var/named/
/var/named/chroot".  Of course df should probably be ignoring filesystems
mounted with the 'bind' option anyway.

This does not appear to be an issue with redhat 5 (it appears that df is fixed
there as the directory permissions are the same).

Comment 2 Adam Tkac 2007-10-31 06:09:00 EDT

Part of 4.6 errata

*** This bug has been marked as a duplicate of 202441 ***

Note You need to log in before you can comment on or make changes to this bug.