Bug 23601 - Warning messages on restart of lpd
Warning messages on restart of lpd
Status: CLOSED WONTFIX
Product: Red Hat Linux
Classification: Retired
Component: distribution (Show other bugs)
7.1
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Crutcher Dunnavant
David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-01-08 12:31 EST by David Lawrence
Modified: 2007-04-18 12:30 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-01-08 12:31:11 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Derek Tattersall 2001-01-08 12:31:08 EST
Many messages of the form:
Starting lpd: Warning - owner/group of '/var/spool/lpd/lp' are 4/0, not 4/7
Warning -   changing ownership '/var/spool/lpd/lp' to 4/7
Warning -   changing ownership '/var/spool/lpd/lp' to 4/7
Warning - owner/group of 'general.cfg' are 4/0, not 4/7
Warning -   changing ownership 'general.cfg' to 4/7
Warning -   changing ownership 'general.cfg' to 4/7
Warning - owner/group of 'postscript.cfg' are 4/0, not 4/7
Warning -   changing ownership 'postscript.cfg' to 4/7
Warning -   changing ownership 'postscript.cfg' to 4/7
Warning - owner/group of 'textonly.cfg' are 4/0, not 4/7
Warning -   changing ownership 'textonly.cfg' to 4/7
Warning -   changing ownership 'textonly.cfg' to 4/7
Warning - owner/group of 'acct' are 4/0, not 4/7
Warning -   changing ownership 'acct' to 4/7
Warning -   changing ownership 'acct' to 4/7
Warning - owner/group of 'log' are 4/0, not 4/7
are printed on starting lpd via "/sbin/service lpd restart"
Comment 1 Crutcher Dunnavant 2001-03-27 15:35:06 EST
this is checkpc rebuild spool files. Its annoying, but harmless, and it is
necessary to see some of the errors that checkpc might detect.

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