Bug 3438

Summary:	cron mail sez' "cannot determine run level"
Product:	[Retired] Red Hat Linux	Reporter:	Jaroslaw Sosnicki <slavko>
Component:	crontabs	Assignee:	Crutcher Dunnavant <crutcher>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.0	CC:	slavko
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2001-04-10 22:00:47 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 Jaroslaw Sosnicki 1999-06-13 21:53:31 UTC

I am getting this root email generated by cron with message
"Can not determine run level"

Comment 1 Jeff Johnson 1999-06-14 14:28:59 UTC

If typing "runlevel" gives the response "unknown", then check
/var/run/utmp* (which is where the current runlevel is stored. You'll
probably see a 0 length (or non-existent) file.

I've seen this behavior with initscripts-4.19 in Raw Hide. Reverting
to the 6.0 initscripts-4.16 fixed my prblem.

Comment 2 Bill Nottingham 1999-06-14 16:59:59 UTC

The initscripts-4.19 (and possibly 4.17, 4.18) problem is
fixed in initscripts-4.20; /var/run/utmp was getting removed
as soon as it was created (oops). Do you have a /var/run/utmp
or /var/run/utmpx?

Comment 3 Jaroslaw Sosnicki 1999-08-28 01:22:59 UTC

Yes I have /var/run/utmp. Since I reported this bug I have upgradet to
initscripts-4.32-2

Thanks for fixing it.