Path: utzoo!attcan!uunet!clyde.concordia.ca!jarvis.csri.toronto.edu!rutgers!cbmvax!grr
From: grr@cbmvax.commodore.com (George Robbins)
Newsgroups: comp.unix.ultrix
Subject: Re: Logging dlogin session to VMS
Message-ID: <9316@cbmvax.commodore.com>
Date: 12 Jan 90 06:51:25 GMT
References: <9269@cbmvax.commodore.com> <9225@cbmvax.commodore.com> <1995@eric.mpr.ca> <7225@shlump.nac.dec.com> <7256@shlump.nac.dec.com> <7403@shlump.nac.dec.com>
Reply-To: grr@cbmvax.commodore.com (George Robbins)
Organization: Commodore, West Chester, PA
Lines: 22

In article <7403@shlump.nac.dec.com> thomas@decwrl.dec.com writes:
> In article <9269@cbmvax.commodore.com>, grr@cbmvax.commodore.com (George
> Robbins) writes:
> > I guess this is an issue, but opening /dev/tty conveys no obvious advantage
> > over duping or using stdin/stdout.
> 
> dlogin does not (repeat that: does not) open /dev/tty.  it uses stdin/stdout.

Try the following experiment 8-)

dlogin >& /tmp/output

The only thing that gets written to the file is the "exit" message, the rest
somehow escaping to your terminal screen.

I dunno exactly what it's doing, but "strings .../dlogin" (3.1 VAX) revealed
the constant "/dev/tty" so that was my initial assumption.

-- 
George Robbins - now working for,	uucp: {uunet|pyramid|rutgers}!cbmvax!grr
but no way officially representing	arpa: cbmvax!grr@uunet.uu.net
Commodore, Engineering Department	fone: 215-431-9255 (only by moonlite)