On Wed, Jun 15, 2005 at 07:16:58PM -0500, David D. Kilzer wrote:
> The log rotation of /var/log/lpr.log leaves the file with incorrect
> ownership and incorrect permissions. The log file is left in this
> state:
The package doing this is sysklogd and those permissions would be ok
as the syslog daemon is the one writing to it.
> -rw-r----- 1 root adm 0 Jun 15 07:48 /var/log/lpr.log
So the question is not why are the permissions like that, they're fine
for a syslog-generated file, but why is checkpc complaining?
I strongly suspect that you've got something configured incorrectly and
it would lead to problems as syslogd has the file open. It might mean
for example that lpd will block as it tries to open the log file.
# fuser -v /var/log/lpr.log
USER PID ACCESS COMMAND
/var/log/lpr.log root 4171 f.... syslogd
So where is /var/log/lpr.log referenced in your printcap or /etc/lprng/
files?
- Craig
--
Craig Small GnuPG:1C1B D893 1418 2AF4 45EE 95CB C76C E5AC 12CA DFA5
Eye-Net Consulting http://www.enc.com.au/ MIEE Debian developer
csmall at : enc.com.au ieee.org debian.org
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
