Bug 174652 - Error upgrading SysVinit-2.85-40 to SysVinit-2.85-42
Summary: Error upgrading SysVinit-2.85-40 to SysVinit-2.85-42
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: sysvinit
Version: 6
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks: FC6Test3Blocker
TreeView+ depends on / blocked
 
Reported: 2005-12-01 03:34 UTC by Jonathan Kamens
Modified: 2014-03-17 02:57 UTC (History)
3 users (show)

Fixed In Version: 2.86-11
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-08-10 19:22:12 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jonathan Kamens 2005-12-01 03:34:41 UTC
I got this while upgrading a bunch of packages, including upgrading
SysVinit-2.85-40 to 2.85-42:

 397:SysVinit		    ########################################### [ 60%]
telinit: timeout opening/writing control channel /dev/initctl

Comment 1 Bill Nottingham 2005-12-01 18:46:10 UTC
Assuming normal system, no chroot, etc?

Comment 2 Bill Nottingham 2005-12-01 18:48:13 UTC
Also, selinux?

Comment 3 Jonathan Kamens 2005-12-01 19:49:40 UTC
Normal system.  Selinux disabled.


Comment 4 Will Woods 2006-07-10 21:51:14 UTC
This happens in FC6-Test2-re20060709.7 during install:

Error(s) installing: SysVinit 2.86 4 i386
telinit: timeout opening/writing control channel /dev/initctl

Comment 5 Bill Nottingham 2006-07-11 16:55:39 UTC
[ -x /sbin/telinit -a -p /dev/initctl -a -f /proc/1/exe -a -d /proc/1/root ] &&
/sbin/telinit u
exit 0

Hm, there's no way that should be valid during install.

Comment 6 Jesse Keating 2006-07-20 21:20:57 UTC
I am not able to replicate this with a clean install of FC5.90.1-re20060719.0.

Will, was yours a clean install, or an upgrade?

Comment 7 Bill Nottingham 2006-08-10 19:22:12 UTC
Fixed in SysVinit-2.86-11.

All together now, "packaging fifos in /dev is silly."


Comment 8 David Lawrence 2007-06-22 02:11:40 UTC
Package name is now sysvinit in Fedora.


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