Re: OSR6... user gets bumped back to a login prompt randomly...

From: Bob Bailin (72027.3605_at_compuserve.com)
Date: 10/31/05 

Date: Mon, 31 Oct 2005 16:27:51 GMT

"foz_67" <foz_67@hotmail.com> wrote in message
news:1130772687.786231.203940@z14g2000cwz.googlegroups.com...
> Hi there,
>
> Just upgraded a server from OSR5.0.5 to OSR6 and I have two users
> constantly getting dropped back to a login prompt. No messages are
> reported in the messages or syslog files and there is no message on the
> screen when the user gets bumped out, just back to a login prompt.
> This can be when the user is running an application or when they're
> just moving from directory to directory.
>
> Connecting one with a PC through it's serial port and running Procomm
> to a Digi Etherlite80 RealPort. And the second is a wyse150 terminal
> connected the same way.
> Server is running OSR6 with osr600mpi and oss702b installed.
> This is on a new Dell PowerEdge 800sc.
>
> This was running great on an NCR S20 connected through a MultiPort.
>
> We're only using IXON IXOFF so just send, receive, and signal ground
> for pinouts.
>
> We've swapped ports and the problem follows the PC. There are 2
> other terminals connected to the same Digi Etherlite80 board that
> don't have this issue.
>
> Emulation on the PC running procomm... vt100
> Emulation on the Wyse150... adds
> Emulation on the Wyse150's that don't have this issue... adds
>
> stty -a on all logged in ports (working ones and the problem ones)
> are the same as below...
>
> speed 38400 baud;
> rows = 0; columns = 0; ypixels = 0; xpixels = 0;
> min = 1; time = 30;
> intr = DEL; quit = ^|; erase = ^h; kill = ^u;
> eof = ^a; eol = ^~; eol2 = <undef>; swtch = <undef>;
> start = ^q; stop = ^s; susp = ^z; dsusp = <undef>;
> rprnt = ^r; flush = ^o; werase = ^w; lnext = ^v;
> -parenb -parodd -parext cs8 -cstopb hupcl cread -clocal -loblk
> -ignbrk -brkint -inpck ignpar -parmrk -istrip -inlcr -igncr -icrnl
> -iuclc
> ixon -ixany ixoff -imaxbel
> -opost -olcuc -onlcr -ocrnl -onocr -onlret -ofill -ofdel
> -isig -icanon -xcase -echo -echoe echok -echonl -noflsh
> -tostop -echoctl -echoprt -echoke -defecho -flusho -pendin -iexten
> -rtsxoff -ctsxon -dtrxoff -cdxon -isxoff xcibrg rcibrg tsetcoff
> rsetcoff
> -isscancode -xscancode
>
>
> I've tried swapping ports.
> I set -hupcl on the port as well to see if DTR is dropping, but
> we're only using send/receive.
>
> Can a cable do this?
> I'm at a loss. Does anyone have any ideas of what I can try?
>
> Thanks for your time.
> Don.

I used to have this problem on our system years ago when we
relied on Wyse terminals connected to Equinox multiport
serial lines. In our case, the sessions would terminate
randomly after receiving a 'quit' signal, even though no one
had ever typed the quit character. I attributed it to random
signal noise on the serial lines that was being misinterpreted
as an actual character.

Try adding:
trap "" 1 2 3

to either /etc/profile or to the user's .profile
to see if the problem goes away.

Bob

Relevant Pages

  • RE: I think Ive been hacked...please help!
    ... > connecting within seconds of boot. ... port scanning the machine from the outside ... experience performing incident response activities, ... one will run netstat and see something listening on ...
    (Incidents)
  • Re: Remote Desktop problems
    ... The> first thing you have to do is setup the router to port forward. ... In the> routers config page you should see settings to> setup port forwarding. ... Once the logon box comes up, you put in a user name>>> that's on the computer your connecting to and its password. ... >>>> laptop on my home network. ...
    (microsoft.public.windowsxp.hardware)
  • Re: Remote Desktop problems
    ... The> first thing you have to do is setup the router to port forward. ... In the> routers config page you should see settings to> setup port forwarding. ... Once the logon box comes up, you put in a user name>>> that's on the computer your connecting to and its password. ... >>>> laptop on my home network. ...
    (microsoft.public.windowsxp.general)
  • Re: Remote Desktop problems
    ... The> first thing you have to do is setup the router to port forward. ... In the> routers config page you should see settings to> setup port forwarding. ... Once the logon box comes up, you put in a user name>>> that's on the computer your connecting to and its password. ... >>>> laptop on my home network. ...
    (microsoft.public.windowsxp.work_remotely)
  • Problem Restated: OPA0 on DS10L
    ... connecting to the OPA0 port. ... normal was TEST 2, connecting from an XP1000. ... NORNS> set host/dte opa0 ...
    (comp.os.vms)