Bug 3092
Summary: | rc.system runs fsck on mounted filesystems. | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | matthew |
Component: | initscripts | Assignee: | David Lawrence <dkl> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | low | ||
Version: | 6.0 | ||
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: | 1999-06-03 22:36:55 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
matthew
1999-05-27 14:48:30 UTC
I hope you mean the rc.sysinit script and not rc.system which does not exist at least not in a stock install of Red Hat. Most of the damaging commands or devices that rc.sysinit run can only be run by root anyway. Normal users would not be able to do any damage and would only see alot of error messages. Now root on the other hand could run the script by accident but I can think of a lot of other ways root could damage the system also. I will that the rc.sysinit script should not have world execute permissions but it will have to stay executable and available by root for the boot up to work correctly. |