Re: [suse-autoinstall] How to define services to enable or disable? [FinanzIT: Viruscheck]

5 Nov 2004


      fraser_bailey@agilent.com schrieb:
...
It should be
<runlevels>
      <default>3</default>
    </runlevels>
Yes, this is what the docs say, but it does not work for me (in 9.1 and 
9.2).

Yast shows that it wants to set runlevel 5. The logfile 
/var/log/Yast2/y2log suggests that a method/function runlevel_proposal 
is called despite the setting in the xml file. This proposal method 
comes up with runlevel 5.
...
-----Original Message-----
From: Stefan Voss [mailto:stefan.voss@itellium.com]
Sent: Friday, November 05, 2004 7:39 AM
To: suse-autoinstall@suse.com
Subject: Re: [suse-autoinstall] How to define services to enable or
disable? [FinanzIT: Viruscheck]
Martin Vidner schrieb:
...
On Thu, Nov 04, 2004 at 12:53:26PM +0100, Hartmut.Dunker@finanzit.com
wrote:
...
I'm using SLES 9. insserv works with my scripts. I've a workaround
for the
autoinst.xml that works but I want to use the services syntax.
It turns out to be a documentation error. The tag should not read
<runlevels> but <runlevel>.
I tried with
<runlevel>
    <default>3</default>
</runlevel>
but autoyast (SuSE 9.2) still insists on runlevel 5.
According to the dtd file (/usr/share/autoinstall/dtd/runlevels.dtd) the
tag should be <runlevels>. Is the dtd file wrong, too?
~> cat /usr/share/autoinstall/dtd/runlevels.dtd
<?xml version="1.0" encoding="UTF-8"?>
<!ELEMENT runlevels (default?, services?)>
<!ELEMENT service (#PCDATA |service_name| service_status| service_start|
service_stop)*>
<!ELEMENT service_name (#PCDATA)>
<!ELEMENT service_status (#PCDATA)>
<!ELEMENT service_start (#PCDATA)>
<!ELEMENT service_stop (#PCDATA)>
<!ELEMENT services (service+)>
<!ATTLIST services
         config:type CDATA #FIXED "list"
...
...
Anas, can you fix the docs please?
...
...
I tried to distribute own services in /etc/init.d and added a
On Thu, Nov 04, 2004 at 08:39:18AM +0100, Hartmut.Dunker@finanzit.com
wrote:
section to
my
...
autoinst.xml to enable this services after installation. For
comparison I
added a section for disable a system service (xdm). This also is
ignored
and the service is enabled after installation. Where is the fault
in my
example?
<configure>
....
    <runlevels>
      <default>3</default>
      <services config:type="list" >
        <service>
          <service_name>configure_system</service_name>
          <service_status>enable</service_status>
        </service>
        <service>
          <service_name>FIT_add_admin</service_name>
          <service_status>enable</service_status>
        </service>
        <service>
          <service_name>xdm</service_name>
          <service_status>disable</service_status>
        </service>
      </services>
    </runlevels>
  </configure>
--
Martin Vidner, developer
SuSE CR, s.r.o.                               e-mail: mvidner@suse.cz
Drahobejlova 27                               tel:+420-296542373
190 00 Praha 9, Czech Republic                http://www.suse.cz
--
To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com
For additional commands, e-mail: suse-autoinstall-help@suse.com
Regards,
    Stefan Voss
Regards,
    Stefan Voss

-- 
Stefan Voss

Mail:  stefan.voss@itellium.com
Tel.:  +49 (0)201/ 727 7443