Issue Details (XML | Word | Printable)

Key: FL-1536
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Normal Normal
Assignee: Distro
Reporter: Jeff Uphoff
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
Foresight Linux

group-core postupdate script keeps turning xdm on in runlevel 3.

Created: 02/Jul/08 03:06 PM   Updated: 11/Jan/13 10:53 PM
Component/s: Base Operating System
Affects Version/s: None
Fix Version/s: None
Security Level: Public (Everyone can see this issue)

Time Tracking:
Not Specified

Environment: fl:2-devel


 Description  « Hide
Despite the following line in /etc/init.d/xdm:
# chkconfig: 5 18 82

And an existing configuration of:

$ chkconfig --list xdm
xdm             0:off   1:off   2:off   3:off   4:off   5:on    6:off

The group-core postupdate script turns xdm on in other, inappropriate runlevels:

[group-core postupdate] + /sbin/chkconfig xdm on

After that command, my xdm/runlevel configuration is incorrect:

$ chkconfig --list xdm
xdm             0:off   1:off   2:on    3:on    4:on    5:on    6:off

The following series of commands demonstrates the source of the problem:

$ chkconfig --del xdm
$ chkconfig --list xdm
service xdm supports chkconfig, but is not referenced in any runlevel (run 'chkconfig --add xdm')
$ chkconfig --add xdm
$ chkconfig --list xdm
xdm             0:off   1:off   2:off   3:off   4:off   5:on    6:off
$ chkconfig xdm on
$ chkconfig --list xdm
xdm             0:off   1:off   2:on    3:on    4:on    5:on    6:off

A runlevel should be added to the 'chkconfig xdm on' command in the postupdate script, as shown below:

$ chkconfig --del xdm
$ chkconfig --list xdm
service xdm supports chkconfig, but is not referenced in any runlevel (run 'chkconfig --add xdm')
$ chkconfig --levels 5 xdm on
$ chkconfig --list xdm
xdm             0:off   1:off   2:off   3:off   4:off   5:on    6:off


 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
No work has yet been logged on this issue.