On Fri 16 Jan 2015 07:44:02 PM CST, mikenash wrote:

The command lspci does nothing on the putty session. I connect to the
server using putty, using a PCOMM session to log onto the 3270 console
and VNC. Since this is a new install I was reviewing /var/log/messages
file and noticed the Failed to start X Display Manager error after the
display manager started the gdm service.
Jan 15 14:35:24 linux234 display-manager[663]: Starting service
Jan 15 14:35:24 linux234 systemd[1]: Failed to start X Display Manager.
The reason I was reviewing the /var/log/messages file was because I was
working with the VNC server. I was unable to start a second session and
I made changes to the /etc/xinetd.d/vnc file to allow a second session.
This worked but the vnc sessions did not logout and remain running.
This behavior was the same before I made any changes. I found the
display manager failure to start and started there. This message was
always there. I can do another install and it will be there. So,
starting gdm is something Suse does and nothing I initiated. Where
would this be initiated from during the boot process?

Via systemd, since it's a remote session set the default to runlevel 3;
systemctl set-default multi-user.target
If you had a display etc and using a graphical desktop, the default
would be set (set-default) to graphical.target.

The command;
systemctl status display-manager.service
Should only be present if it's trying to start up a graphical session,
so this should show as dead.

You can also analyze the startup with systemd-analyze (blame and
critical-chain to see what is starting, when and how long it's taking.

Since your running vnc there should also be some sort of service file
for this.

Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.28-4-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below... Thanks!