Bug 3754 – Constant errors in /var/log/secure

Bug 3754 - Constant errors in /var/log/secure

Summary:	Constant errors in /var/log/secure

Status:	CLOSED NEXTRELEASE

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	pam (Show other bugs)
Sub Component:
Version:	6.0
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Michael K. Johnson
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	1999-06-26 22:59 EDT by lyte
Modified:	2008-05-01 11:37 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	1999-07-30 11:16:53 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 lyte 1999-06-26 22:59:30 EDT

Hi,
From the moment I had installed 6.0 I keep on getting this error in my /var/log/secure and I would like to know how to fix it because it just fills up the log file. The error is:
Jun 26 21:49:26 redhat pam_console[3928]: console file lock already in place /var/lock/console.lock

I have tried removing the lock file and that didnt work. It doesnt seem to happen when root logs in, only when my user "lyte" logs in.
Thanks in advance for any help.
Joey.

Comment 1 Cristian Gafton 1999-07-02 16:37:59 EDT

assigned to MkJ

------- Additional Comments From   07/23/99 22:41 -------
Has there been any new developments in this or do you not know what is causing the errors? Thank you for your time.

Comment 2 Michael K. Johnson 1999-07-30 10:41:59 EDT

It's an informational message, not a debugging message.  I'll
change it to a debug level message in the next release of pam
and your problem will go away.

Comment 3 Michael K. Johnson 1999-07-30 11:16:59 EDT

The next release of pam will have this change.

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