Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 76342

Summary:	mgetty logrotate config fills /var/log
Product:	[Retired] Red Hat Linux	Reporter:	Mika Ilmaranta <ilmis>
Component:	mgetty	Assignee:	Nalin Dahyabhai <nalin>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.3
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-02-21 18:49:59 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 Mika Ilmaranta 2002-10-20 13:17:13 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2a) Gecko/20020913

Description of problem:
mgetty 1.1.28-3 logrotate config is filling /var/log/ with
mgetty.log.ttyS?.x.x.x.x... files where x is any single digit number 0-9.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.Everytime logrotate is run.
2.
3.
	

Additional info:

Maybe mgetty's log file naming convention should be changed from
mgetty.log.ttyS? to mgetty.ttyS?.log to allow the use of * in
/etc/logrotate.d/mgetty. It simply does not work with * as last component of
what to rotate. Other possible solution would be to change logrotate so it would
not touch anything that ends with number.

For now fixed with removing * from mgetty's logrotate config and giving exact
paths to log-files.

Comment 1 Miguel Armas 2002-11-07 10:33:09 UTC

It can be fixed just changing /var/log/mgetty.log.tty*   
for /var/log/mgetty.log.ttyS? in /etc/logrotate.d/mgetty

Comment 2 giulioo 2003-02-20 18:50:01 UTC


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

Comment 3 Red Hat Bugzilla 2006-02-21 18:49:59 UTC

Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.