> AK> You should open another ticket, or it'll make the problem complexed. > I'm guessing that maybe both problems are related, and fixing the latter > will fix the former.
You can guess but I can't guess because of less information. You should describe how you handle rcconf and how you find the problem at least. > AK> BTW, rcconf saves the service name and its number(NN of > AK> /etc/rc?.d/[SK]NNname]) in /var/lib/rcconf/services. If you purge > AK> rcconf, this file is deleted. > Yes. > AK> When you purge and install rcconf again, this file isn't recoverd. > AK> So, rcconf can't recognize off stated service if you set off before. > Yes. > AK> If you don't want to do so, you must not purge rcconf. > Yes. > What I'm saying is that a fresh install of rcconf does not recognize any > "off" services at all. > Please try this: > rcconf --list|grep -c off > rcconf --list|grep -c on > aptitude purge rcconf > aptitude install rcconf > rcconf --list|grep -c off > rcconf --list|grep -c on > Note that the services that were formerly off are now > _totally unreachable by rcconf_... _disappeared_, > "沉沒大海，尋無回"。 > Do you mean the above steps describe fresh install of rcconf? I've already described why rcconf can't find off state services by purge and install(probably you means 'fresh install'). I improved off state finding by update-rc.d disable that I mensioned in 2.3 and I'll close this bug because this may solve your problem. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
