Bill Shannon wrote:
> 
> Glenn Fowler wrote:
> > On Wed, 12 Mar 2008 17:33:11 -0700 Bill Shannon wrote:
> >> Bill Shannon wrote:
> >>> Glenn Fowler wrote:
> >>>> On Mon, 10 Mar 2008 20:03:30 -0700 Bill Shannon wrote:
> >>>>> Who's invoking "tty -l" when I use ksh93?  It's not in any of my
> >>>>> dot files.
> >
> >> According to truss, this message is coming from ksh93 itself.
> >
> > if its the builtin tty from -lcmd it would show up in the same process
> > there must be a tty -l call in some script somewhere
> 
> I haven't found it.  How can I find it if it's using a builtin?

All AST tools (AST="Advanched Software Technology", which is more or
less a superset of the upstream package which contains ksh93) support
the "--man" option, e.g. you can test for the builtin version of "tty"
via $ tty --man # ; the official ksh93 way to test for it is $ builtin |
fgrep tty # to check whether the "tty" builtin is enabled by default and
whether it's bound to a path...

> It's not in the new /etc/ksh.kshrc.

What about /etc/profile ?

> The only occurrences of the word "tty" in my dots files are:
> 
> $ grep -w tty .profile .kshrc
> .profile:else           # normal tty login
> .kshrc:if [ `tty` != /dev/console ]

AFAIK I found the problem; the builtin "tty" has a small glitch which
causes it to always print "not on an active synchronous line":
-- snip --
$ tty                            
/dev/pts/2
not on an active synchronous line
-- snip --

[snip]
> I know everyone's fascinated by this strange problem, but I'm sure it
> will be easily found when someone fires up a debugger on ksh93.  But
> really, it's not the problem I'm worried about.  The problem I'm
> worried about is the problem I filed the bug report for!  Anyone looking
> into that?

I tried to look into that problem... the trouble is that I can't
reproduce it on my side... ;-(

----

Bye,
Roland

-- 
  __ .  . __
 (o.\ \/ /.o) roland.mainz at nrubsig.org
  \__\/\/__/  MPEG specialist, C&&JAVA&&Sun&&Unix programmer
  /O /==\ O\  TEL +49 641 7950090
 (;O/ \/ \O;)

Reply via email to