Bug 114590

Summary:	Error message while first boot after syslog daemon started
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Lars Müller <lmuelle>
Component:	Basesystem	Assignee:	Lars Müller <lmuelle>
Status:	VERIFIED INVALID	QA Contact:	Klaus Kämpf <kkaempf>
Severity:	Normal
Priority:	P5 - None	CC:	werner
Version:	Beta 4
Target Milestone:	---
Hardware:	Other
OS:	All
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Lars Müller 2005-08-31 21:54:45 UTC

I've updated from Beta 3 to Beta 3 and while the first boot I got:

Starting syslog services                                                 [done]
No such file or directory

Comment 1 Klaus Kämpf 2005-09-01 06:42:12 UTC

So you updated - then its not the 'Installation' component.  
And its after reboot - so its not update  
Oh, its the boot scripts -> assigning to basesystem (mmj ?)

Comment 2 Lars Müller 2005-09-01 12:28:32 UTC

This is no syslog issue.

This only happens after the first boot after the installation/ update.

Comment 3 Marius Tomaschewski 2005-09-01 15:43:08 UTC

Yes, you are right Lars.

The syslog init script executes "rc_status -v" (and rc_exit) as
its last command. Because the "done" message is shown before the
error message, it can't happen inside of the syslog script.

Comment 4 Mads Martin Joergensen 2005-09-05 15:53:35 UTC

Werner, an idea?

Comment 5 Dr. Werner Fink 2005-09-05 16:45:13 UTC

If this is not bug #113002 I don't know.

I'd like to see

   rpm -q --changelog sysvinit | head -n 10

Comment 6 Dr. Werner Fink 2005-09-06 09:42:20 UTC

Lars? I need that info.

Comment 7 Lars Müller 2005-09-06 15:32:19 UTC

It's on my system at home and I just returned to Nuremberg.  I'll provide the
info later today.

Comment 8 Andreas Jaeger 2007-04-25 20:19:08 UTC

Lars, what is the status here?

Comment 9 Lars Müller 2009-09-07 16:24:28 UTC

As I no longer know on which system I've seen this effect I close the report as invalid.