<quote who='Doug Farmer' date='Thursday 11 December 2008'>
> Good Morning,
>
> I am a bit out of my element here as I usually only work on HP UNIX
> boxes.
>
> I have a problem with a Linux box that was recently updated to release
> 7.1.13 of UniData. Since the upgrade, connections to the machine using
> UniObjects are aborting. I think I traced this down to a possible issue
> with the environment variables in the UniObjects session. I am missing
> the environment setting for UDTBIN and UDTPATH.
>
> The scenario is this.
>
> Using a UniObjects connection, a subroutine is run on the host.
>
> This subroutine launches a phantom process that runs in sleep cycles,
> waking up to process data as needed. The UniObjects connection is
> closed (it is only used to launch the phantom).
>
> The phantom inherits the environment from the UniObjects connection.
>
> One of the first things the phantom does is to call the UniData
> subroutine WW.SB.RB. The subroutine never returns and the phantom
> stops. My guess is the subroutine is aborting because of a missing
> UDTBIN or UDTPATH variable. (I wrote the environment variables to a
> debug file prior to calling the subroutine).
>
> This all worked till the upgrade to UniData 7.1.13. So I think
> something got mashed in the startup process and the environment
> variables are not setup when UNIRPCD is started.
>
> Any clues as to where I should start looking?
Doug:
Not to state the obvious, but have you looked at the $UDTBIN/startunirpcd
script? It mucks around with UDTBIN based on your unishared contents, but
you could also hard-code some values here (althought that would create a
future upgrade problem itself...)
--
Jeff Butera, Ph.D.
Administrative Systems
Hampshire College
[EMAIL PROTECTED]
413-559-5556
"Where I'm from, we believe all sorts of
things that aren't true. We call it 'history'."
The Wizard, Wicked
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
