[comp.protocols.iso.dev-environ] upgrade 6.1 -> 6.8

Hans.Klunder@RC.TUDelft.nl (05/03/91)

Hello,

I have a SUN 4/330 (4.1.1) running isode-6.1 over sunlink X.25
and tcp/ip. This works great. 

Last week I tried to ugrade to isode-6.8, this looked ok,
but when I run isode-test I get 1 successful connection and then
the tsapd dies.

Has anyone seen this before and , even better, does anybody
know how to fix this behaviour ?


Thanks in advance,

Hans

-----------------------------------------------------------------
Hans Klunder                                   tel: +31 15 785857
System Support                                 fax: +31 15 783787
Rekencentrum                   E-mail: Hans.Klunder@RC.TUDelft.nl
TUdelft                      
P.O.box 354
2600 AJ Delft
The Netherlands

A.Macpherson@stl.stc.co.uk (Andrew Macpherson, Postmaster) (05/04/91)

Perhaps a silly question, but was the tsapd in background?

If you were running it in the foreground (with stderr to the tty) then
it is supposed to die after the first connection.


Hans.Klunder@rc.tudelft.nl wrote:
| Hello,
| 
| I have a SUN 4/330 (4.1.1) running isode-6.1 over sunlink X.25
| and tcp/ip. This works great. 
| 
| Last week I tried to ugrade to isode-6.8, this looked ok,
| but when I run isode-test I get 1 successful connection and then
| the tsapd dies.
| 
| Has anyone seen this before and , even better, does anybody
| know how to fix this behaviour ?
| 
| 
| Thanks in advance,
| 
| Hans
| 
| -----------------------------------------------------------------
| Hans Klunder                                   tel: +31 15 785857
| System Support                                 fax: +31 15 783787
| Rekencentrum                   E-mail: Hans.Klunder@RC.TUDelft.nl
| TUdelft                      
| P.O.box 354
| 2600 AJ Delft
| The Netherlands

rlang@NISC.SRI.COM (Ruth Lang) (05/04/91)

Date: Fri, 03 May 91 19:09:53 +0100
From: Andrew Macpherson (Postmaster) <A.Macpherson@stl.stc.co.uk>

> Perhaps a silly question, but was the tsapd in background?
> 
> If you were running it in the foreground (with stderr to the tty) then
> it is supposed to die after the first connection.

I've observed similar behaviour to that reported by Hans Klunder.  
At SRI, we're running 6.8 on a Sun 4/390 w/ SUNOS 4.1.1.  tsapd dies
after reporting utctime whether it's running in foreground or background.

Ruth Lang

cudep@warwick.ac.uk (Ian Dickinson) (05/07/91)

In article <9105040059.AA00843@ws28.nisc.sri.com> rlang@NISC.SRI.COM (Ruth Lang) writes:
>I've observed similar behaviour to that reported by Hans Klunder.  
>At SRI, we're running 6.8 on a Sun 4/390 w/ SUNOS 4.1.1.  tsapd dies
>after reporting utctime whether it's running in foreground or background.

Under SunOS 4.1 onwards, any program which starts terminal sessions,
such as iso.vtd from tsapd needs to have a new session identifier as
well as being disassociated from the terminal.

Maybe starting up with:

setsid -b tsapd >/dev/null 2>&1

will cure it?

This is similar to the Sunlink 6.0 X.25 which uses setsid with x29.

Cheers,
-- 
\/ato. Ian Dickinson.   / /// Send your dollars, Homeboy, \\\ \     /'\  /`\
vato@warwick.ac.uk     ( (((  I'm a Pink Foetus for "Bob"  ))) )   /^^^\/^^^\
vato@tardis.cs.ed.ac.uk \ \\`------X.500-Check-me-out-----'// /   /TWIN/TEATS\
@c=GB@o=University of Warwick@ou=Computing Services@cn=Ian Dickinson  /       \