Re: Problem running X start file
From: Nigel Pain (
)
Date: Tue May 04 2004 - 05:54:08 EDT
*******************************************************************************************************************************************************
This email and any files transmitted with it are intended solely for the use of the individual or entity to whom they are addressed.
*******************************************************************************************************************************************************
> However, the question is why what we have run originally does
> not work for one server and works for others.
I would be more inclined to wonder why what was originally used worked
at all: the new behaviour is more consistent with my understanding of
the way things work.
***************************************************
Nigel Pain
Scottish Executive
Analytical Services Team
Victoria Quay
EDINBURGH
EH6 6QQ
UK
Tel +44 131 244 7237
Mailto:
Website: http:\\www.scotland.gov.uk
> -----Original Message-----
> From: Title: ExceedUsers [mailto:
]
> On Behalf Of Parij, Arkadi (Arkadi)
> Sent: 30 April 2004 01:55
> To:
> Subject: Re: [EXCEEDUSERS] Problem running X start file
>
>
> *******************************************************************
> This email has been received from an external party and
> has been swept for the presence of computer viruses.
> *******************************************************************
>
> Jim,
>
> Thanks for your reply.
> Your suggestion have worked for Xclock.
>
> However, the question is why what we have run originally does
> not work for one server and works for others.
>
> It might represent another problem we are seeing when we run
> other X Apps, like HP OV (Network Node Manager), from X
> session with X Start file attached with Multiple Window
> setting. Occasionally one of the application windows gets
> dropped with the error message saying that connection to X
> server is lost.
>
> This. also happens from time to time when we connect to the
> server with Exceed query and run HP OV in full CDE environment.
>
> We experience this behaviour with Exceed 7 and 8.0.0.
>
> Any ideas,
>
> Regards,
>
> Arkadi Parij
> OSS Consultant
> * Lucent Worldwide Services
> Tel: +61 2 9491 6671
> Email:
>
> ***************************************************************
> NOTE: This email (and/or its attachments) contains
> information belonging to the sender, which may be
> confidential, proprietary and/or legally privileged. The
> information is intended only for the use of the
> individual(s) or entity(ies) named above. If you are not the
> intended recipient, you are hereby notified that any
> disclosure, distribution or taking of any action in reliance
> on the content of this is strictly forbidden. If you have
> received this e-mail in error please immediately notify the
> sender identified above.
> **************************************************************
> **************
> *********************
>
>
> -----Original Message-----
> From: Jim Frost [mailto:
]
> Sent: Friday, April 30, 2004 2:22 AM
> To: 'Title: ExceedUsers'
> Subject: RE: [EXCEEDUSERS] Problem running X start file
>
>
> Parij,
>
> Try adding an ampersand "&" to the end of your command line.
>
> In fact you don't need to run the xterm. Try the following
> command line:
>
> /usr/openwin/bin/xclock -display @D &
> or
> /bin/nohup /usr/openwin/bin/xclock -display @D &
>
> This will allow the command to run detached from the telnet
> connection. The telnet connection closes after 10 seconds.
> The /bin/nohup keeps the closing of the telnet connection
> from killing the xclock (child process).
>
> Regards,
> Jim Frost
> Hummingbird
>
> -----Original Message-----
> From: Parij, Arkadi (Arkadi) [mailto:
]
> Sent: Thursday, April 29, 2004 4:01 AM
> To:
> Subject: [EXCEEDUSERS] Problem running X start file
>
>
> Hello There,
> .
> We have Exceed 8 and. have come across with a strange problem
> trying to connect to a Sun Server (E450) and run some X
> applications on Solaris 8 from X start file with the
> following configuration:
> Start Method: TELNET (TCP/IP)
> Program Type: X Window
> Command: /usr/dt/bin/dtterm -display @D -e
> /usr/openwin/bin/xclock
>
> It starts OK and runs for a about 10 sec and then the
> connection is dropped. Now, if we change "Close" timeout
> setting from default (10 sec) to let say 120 sec it will
> work for about 120 sec and then will be dropped.
>
> Interestingly, when we run this X start file against
> different Sun Server
> (E450) with Solaris 8 it works fine all the time.
>
> Is there anything we need to change/set on the server?
>
> Any suggestions/comments would be much appreciated.
>
> Arkadi Parij
>
> PLEASE NOTE: THE ABOVE MESSAGE WAS RECEIVED FROM THE INTERNET.
>
> On entering the GSi, this email was scanned for viruses by
> the Government Secure Intranet (GSi) virus scanning service
> supplied exclusively by Energis in partnership with MessageLabs.
>
> Please see
> http://www.gsi.gov.uk/main/notices/information/gsi-003-2002.pd
f for further details.
In case of problems, please call your organisational IT helpdesk
The original of this email was scanned for viruses by the Government Secure Intranet (GSi) virus scanning service supplied exclusively by Energis in partnership with MessageLabs.
On leaving the GSi this email was certified virus-free
This archive was generated by hypermail 2b29
: Mon May 31 2004 - 23:54:01 EDT
|
