Ole, The variable DISPLAYMANAGER_STARTS_XSERVER is being set when configuring X11 which happens after autoyast writes the sysconfig variables... One solution is to change the order how the clients are executed. This can be done in the control.xml file available on the root of the installation source. simply put the 'x11' module section before 'autoconfigure', for example in 9.2 the diff would be: --- control.PROF.xml 27 Sep 2004 11:49:45 -0000 1.16 +++ control.PROF.xml 5 Feb 2005 22:14:42 -0000 @@ -510,12 +510,12 @@ </module> <module> <label>System Configuration</label> - <name>autoconfigure</name> + <name>x11</name> + <arguments>false,false</arguments> </module> <module> <label>System Configuration</label> - <name>x11</name> - <arguments>false,false</arguments> + <name>autoconfigure</name> </module> <module> <label>Clean Up</label> I will change that for the next version. Thanks, Anas Ole Streicher wrote:
Hi,
I have a mysterious problem with the sysconfig section:when I use the following section
<sysconfig config:type="list">
DISPLAYMANAGER_REMOTE_ACCESS /etc/sysconfig/displaymanager yes DISPLAYMANAGER_STARTS_XSERVER /etc/sysconfig/displaymanager no DISPLAYMANAGER_XSERVER_TCP_PORT_6000_OPEN /etc/sysconfig/displaymanager yes </sysconfig> YAST2_LOADFTPSERVER /etc/sysconfig/onlineupdate no all system variables are set except the DISPLAYMANAGER_STARTS_XSERVER which still has the default value "yes". Is the handling of this section buggy, and how could one work around this?
System is SuSE-9.2.
Best regards,
Ole