Hi Shaddy
I am also using Solaris 7/Win98 and I have solved my login problem using what you
have mentioned in the other mail, that is, to use a script to restart the server
whenever it is down. I agree that it does not seem too be an elegant solution, but
nevertheless, it works. One point for other people who would like to use this method,
you have to run this script as root. Otherwise, your server cannot be restarted. This
is due to the permission problem of .X11-unix reverting back to its original value
after the user has logged out. Anyway, I think the best solution for you is still to
run it as a root process. Simple and efficient. Can't your sysadmin help you with it?
On Wed, 25 July 2001, "Baddah, Shaddy" wrote:
>
> I run Xvnc on a Solaris 7 host of which I have no admistrative control. This
> off course restricts my ability to create the unix-socket required to access
> the display at the unix address. So, I pass the -pn "accept failure to
> listen on all ports" and use only the inet display name. When I attempt to
> use XDMCP with the server in this mode, I am running into the following
> problem. If I pass the -query localhost "contact named host for XDMCP"
> option, the dtlogin XDM acknowledges the query, but attempts to manage the
> display using the unix display name. The following exert from the
> /var/dt/Xerrors log file demonstrates this.
>
> Thu Jul 26 11:16:36 2001
> error (pid 12512): Server open attempt #0 failed for :9, giving up
>
> My work around for a considerable period of time has been, to omit the
> option all together (i.e. unmanaged display) and to manually call the
> /usr/dt/config/Xsession.ow script, emulating what dtlogin would do with a
> new login session. I have continued to use this workaround because I
> suspected that dtlogin might be determining that the query came from a local
> display, and automatically attempting to connect to it through the
> unix-socket, and I lacked the time to verify this 100% and find a workaround
> with dtlogin.
>
> My questions are... has someone actually run into this same problem? How
> does the XDM know which display and the display name it should manage? If it
> is dtlogin, is there a configuration to workaround this? Any other
> workarounds?
>
> Many thanks,
> Shaddy
>
>
> -------------------------------------------------------------------------
> This message may contain privileged and/or confidential information subject
> to a confidentiality agreement or copyright material of Clarity
> International Ltd or third parties. You should only re-transmit, distribute
> or commercialise the material if you are authorised to do so.
> If you are not an authorised recipient of this email, please contact Clarity
> International Ltd immediately by return email or by telephone on +61-2-9925
> 5000.
> In such case, you may not read, print, store, copy or deliver this message
> to anyone, and you should not act in reliance on this email or any
> attachment to it.
> Clarity provides no warranty that the material contained in this email or
> any attachment to it is free from any virus, defect or error. Opinions in
> this message are those of the sender and unless stated otherwise, are not
> endorsed by Clarity.
> ---------------------------------------------------------------------
> To unsubscribe, send a message with the line: unsubscribe vnc-list
> to [EMAIL PROTECTED]
> See also: http://www.uk.research.att.com/vnc/intouch.html
> ---------------------------------------------------------------------
Find the best deals on the web at AltaVista Shopping!
http://www.shopping.altavista.com
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
