Bug 421741

Summary: Wine starts at wrong level
Product: [Fedora] Fedora Reporter: Nigel Horne <njh>
Component: wineAssignee: Andreas Bierfert <andreas.bierfert>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: 8   
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: 2007-12-12 15:22:32 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 Nigel Horne 2007-12-12 15:09:02 UTC 
Description of problem:
Wine is enabled at levels 2 3 4 5, but it makes no sense to run programs under
wine unless X is up, so it should only be enabled at level 5.


Version-Release number of selected component (if applicable):
wine-0.9.49-1.fc8

How reproducible:
100%


Steps to Reproduce:
1. Boot to init level 3
2. /sbin/service wine status
3.
  
Actual results:
It's enabled

Expected results:
It shouldn't be

Additional info:
Comment 1 Andreas Bierfert 2007-12-12 15:22:32 UTC 
Quoting from /etc/inittab:

#   2 - Multiuser, without NFS (The same as 3, if you do not have networking)
#   3 - Full multiuser mode
#   4 - unused
#   5 - X11

All these are _valid_ runlevels for starting X and applications that need X
(actually one could argue if 1 is also valid). Another point: Wine in general is
not restricted to be used with X. Despite that this setup is ok there is no
speed impact because it is not wine that gets started but just the binary
handler is inserted into the kernel.