Bug 169938

Summary:	RFE: timestamp /tmp/syslog entries
Product:	[Fedora] Fedora	Reporter:	James Laska <jlaska>
Component:	anaconda	Assignee:	Chris Lumens <clumens>
Status:	CLOSED WONTFIX	QA Contact:	Mike McLean <mikem>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	herrold, jturner
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:	2006-01-31 20:32:36 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:
Bug Depends On:
Bug Blocks:	150221

Description James Laska 2005-10-05 14:12:19 UTC

# TREE nightly/rawhide-20051005
# ARCH *all*

Was thinking perhaps timestamping /tmp/syslog entries might be useful.  Seems
like it would be a minimal change, that might proof handy in debugging
dhcp/network timeout issues.  We already go about timestamping entries in
/tmp/anaconda.log.  I'm trying to make sense out of doklog() function in
loader2/init.c which looks like it forks and sets up a socket to handle the logging?

Thoughts?

Comment 1 Chris Lumens 2005-10-07 18:41:05 UTC

Yes, doklog handles the logging from the kernel and writes it to /tmp/syslog. 
It would be pretty trivial to add timestamping here as well.  Somewhere on the
giant list of things to do is also to add remote syslogging support to the
loader to match what the second stage is capable of.

Comment 2 Jeremy Katz 2006-01-31 20:32:36 UTC

Not going to do this.