LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Mandriva (https://www.linuxquestions.org/questions/mandriva-30/)
-   -   Activating compat-mode for Services (https://www.linuxquestions.org/questions/mandriva-30/activating-compat-mode-for-services-464693/)

samorris 07-16-2006 09:48 PM

Activating compat-mode for Services
 
I have installed Mandriva 2006 and have upgraded X Windows to 7.1 and KDE to 3.5.3. I have also upgraded rpm, urpmi, gcc and a number of other packages. The problem I now have is that every time I boot and shutdown I get the message "Activating compat-mode for ..." for every service in /etc/rc.d/rc5.d irrespective of whether the service has been set to start at boot time or not. Can anybody shed some light on what I have upgraded that may be causing this problem, or alternatively what config file may have been installed with one of the upgrades which needs to be activated. Thankyou.

Matir 07-18-2006 10:47 AM

It may be that nsswitch.conf is set up for compat mode and as such, is preparing for any service that may be started. Do the services actually start at any point?

samorris 07-18-2006 10:00 PM

Thankyou for the response. nsswitch was one of the packages that was upgraded, but I thought I had merged the nsswitch.conf.rpmnew into the existing nsswitch.conf but I may not have. In any case, some of the services such as 'firestarter', 'cups', 'wine', 'sound' are started at boot time and seem to function ok. Other services like 'iptables', 'ipv6tables', 'numlock' are never started, but the messages still appear for these, as well as the services which are started, at both boot time and shutdown.

samorris 07-20-2006 12:37 AM

I have checked nsswitch.conf and the 'services' entry is set to 'files'. I tried changing it to 'nisplus files' but it made no difference. I suspect the messages are being produced by whatever application (at the moment I have no idea what this is) is stating the services scripts, because I suspect as part of the upgrade to Xorg, the XPRINT package I had installed was removed. But the scripts for each of the run levels it was set to start in were left behind as invalid pointers, because the init.d script for XPRINT was removed with the deinstall. As soon as the machine entered runlevel 5 at boot a message was produced about being 'unable to stat S61XPRINT' followed by all the messages highlighted. I removed all of the XPRINT symbolic links which then got rid of that message at boot time. The other thing which I forgot to mention, which may or may not be relevant, is that I am now running Kernel 2.6.16-3.

samorris 07-21-2006 12:28 AM

Since my last update I have upgraded the CUPS environment and the message is no longer produced for this application. So it looks like that once I have fully upgraded kde to the 3.5.3 version that is on the cooker mirrors, I may have to upgrade every package containing the services is question, if an upgrade exists. The two packages that have me concerned in this process are SYSLOG and RC.LOCAL. If these two are actually running in compatibility mode, what are they not doing that they should be?
One other thing that is a concern at the moment, is that at boot time UDEV keeps complaining that it can't find /BIN/FLOCK, and I don't know what impact this has if any.

samorris 08-08-2006 10:18 PM

problem identified
 
I have now been on the Mandriva Cooker Archives and have found an entry which explains these messages. It appears that now boot/shutdown init processing runs scripts in parallel mode if possible, and produces this message for each script which has not been designed to run in this mode.


All times are GMT -5. The time now is 10:12 AM.