i'm in runlevel "wireless" which has two stacked runlevels ("network" and "default"). all services in the stacked runlevels are listed as manually started. Runlevel: wireless network [ started ] net.wlan0 [ started ] Stacked Runlevel: network rpcbind [ started ] xinetd [ started ] openvpn [ started ] samba [ started ] ntpd [ started ] sshd [ started ] Stacked Runlevel: default metalog [ started ] acpid [ started ] xdm [ started ] alsasound [ started ] cpufrequtils [ started ] dcron [ started ] local [ started ] Dynamic Runlevel: hotplugged Dynamic Runlevel: needed sysfs [ started ] udev-mount [ started ] xdm-setup [ started ] dbus [ started ] hald [ started ] xdm [ started ] alsasound [ started ] rpcbind [ started ] Dynamic Runlevel: manual xinetd [ started ] metalog [ started ] openvpn [ started ] cpufrequtils [ started ] dcron [ started ] ntpd [ started ] samba [ started ] sshd [ started ] local [ started ]
Please test 0.6.1-r1 if you can still reproduce please reopen.
considering no one committed fixes for this, i doubt it started working. and indeed, with 0.6.1-r1: Runlevel: nonetwork metalog [ started ] dcron [ started ] acpid [ started ] local [ started ] Dynamic Runlevel: hotplugged net.wlan0 [ started ] Dynamic Runlevel: needed udev-mount [ started ] device-mapper [ started ] xdm-setup [ started ] Dynamic Runlevel: manual dmcrypt [ started ] dnsmasq [ started ] ntp-client [ started ] openvpn [ started ]
Cosmetic error I think, but should be fixed before going stable.
Still an issue in 0.7.0?
(In reply to comment #4) > Still an issue in 0.7.0? I'm sure it is since no one has worked on this bug yet. Actually I'm not quite sure how to set up to test this since I haven't used stacked runlevels.
just create symlinks: cd /etc/runlevels mkdir foo mv default/local foo/ ln -s ../foo default/foo
This bug is even more weird than I first thought. I'm in the default runlevel, with a stacked runlevel called test1 which has very simple services, x y and z which just print a message saying they have started: cd /etc/runlevels mkdir test1 rc-update add x test1 rc-update add y test1 rc-update add z test1 rc rc-status shows the following: Runlevel: default net.eth0 [ started ] net.tap0 [ started ] syslog-ng [ started ] ntpd [ started ] netmount [ started ] sshd [ started ] dbus [ started ] udev-postmount [ started ] vixie-cron [ started ] local [ started ] Stacked Runlevel: test1 z [ started ] y [ started ] x [ started ] Dynamic Runlevel: hotplugged Dynamic Runlevel: needed sysfs [ started ] udev-mount [ started ] Dynamic Runlevel: manual z [ started ] y [ started ] The stacked runlevel is there, but all of the services except one show up also in the manual runlevel.
Mor e info: (In reply to comment #7) > This bug is even more weird than I first thought. > I'm in the default runlevel, with a stacked runlevel called test1 which > has very simple services, x y and z which just print a message saying > they have started: > cd /etc/runlevels > mkdir test1 > rc-update add x test1 > rc-update add y test1 > rc-update add z test1 ln -s ../test1 default/test1
What we appear to be getting is duplication of services in the listing. I just noticed that in the initial description, the services which are listed as manually started are also listed in their appropriate run levels.
This is a display issue that needs to be fixed, but it should not block stabilization. I am removing it from the tracker.
I just submitted another bug report which fixes some other issues and should resolve these too - see bug 467368 for more details. I'd really appreciate wider testing if possible. Thanks!
(In reply to comment #11) > I just submitted another bug report which fixes some other issues and should > resolve these too - see bug 467368 for more details. I'd really appreciate > wider testing if possible. Thanks! I can confirm that the patch on bug #467368 resolves this issue.
I am closing this since there has been no more activity.
