Xmanager Forum

XBrowser Problem

Last post: Friday, July 13, 2007 6:27 PM by Steven, 5 reply

Sunday, January 13, 2002 11:38 PM - David Walters

XBrowser Problem

I have to machines running RedHat Linux 7.2. When I run XBrowser, I get a status of "Linux 2.4.7-10" for one machine, but I get "Willing, but /etc/X11/xdm/Xwilling failed" for the other machine. Both machines were setup off the same disks and are running "KDE Version 2.2-10" any ideas??
Monday, January 14, 2002 12:09 AM - Michael

Re: XBrowser Problem

Maybe, the following command helps you to solve your problem.

as root,

# chmod 755 /etc/X11/xdm/Xwilling

Good luck!!
Monday, January 14, 2002 1:17 AM - David Walters

Re: Re: XBrowser Problem

The permissions on that file were already "755".
Monday, January 14, 2002 11:01 AM - Michael

Re: Re: Re: XBrowser Problem

Sorry for my helpless answer.

I hope following steps help you.

1. Open /usr/share/config/kdm/kdmrc file.
2. Comment out "Willing" option as following:
3. restart your linux machine.

Avobe steps prevent "/etc/X11/xdm/Xwilling" from working.
And Xbrowser get "Willing to manage" message instead of "Willing, but /etc/X11/xdm/Xwilling failed" message.

Friday, July 13, 2007 5:57 PM - Matt

Re: XBrowser Problem

We use Xbrowser to connect to all our different unix boxes (different flavours of unix).
Several of the unix boxes are running AIX 5.2 and show the status correctly in the status column.
One particular AIX box sometimes reports the message "Willing to Manager" in this column. Strangely this appears when we cannot connect to it.
Is it possible to get a full explanation about this message and why it would appear when we cannot connect.
If we log into it via the console and open a terminal window, this message dissapears and we get the correct status again.

Any ideas?
Friday, July 13, 2007 6:27 PM - Steven

Re: Re: XBrowser Problem

Hi there,

It seems there are two display managers running on your server. "Willing to manage" message is produced by xdm which is an old counter part of dtlogin. This can cause conflicts when using with Xmanager.

Disable or kill the xdm process and leave the dtlogin process enabled.