Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!snorkelwacker!think!samsung!cs.utexas.edu!rutgers!cbmvax!grr
From: grr@cbmvax.commodore.com (George Robbins)
Newsgroups: comp.unix.ultrix
Subject: Re: Logging dlogin session to VMS
Message-ID: <9225@cbmvax.commodore.com>
Date: 5 Jan 90 18:24:15 GMT
References: <1995@eric.mpr.ca> <7225@shlump.nac.dec.com>
Reply-To: grr@cbmvax.commodore.com (George Robbins)
Organization: Commodore, West Chester, PA
Lines: 28

In article <7225@shlump.nac.dec.com> thomas@decwrl.dec.com writes:
> In article <1995@eric.mpr.ca>, murphy@eric.mpr.ca (Gail Murphy) writes:
> > I would like to connect to a VMS machine from an Ultrix workstation
> > and log the session...
> 
> I could change dlogin to set the logfile to be unbuffered but that
> would be at the cost of slowing down dlogin.  Or maybe fflush the
> logfile once dlogin has been idle for 30secs or so.  (which would
> be easy to tie into the select call).  And/or when you escape to the
> dlogin command menu?  Any other ideas?

Opinion:

It seems to me that the -l switch is used so infrequently that setting the
log to unbuffered or doing a fflush after each time your see that you have
written a line terminator to the terminal output wouldn't really have any
serious performance impact.  You might try it and see if there's any noticable
slow down.

BTW, you might want to think about what dlogin is doing for input and output.
It appears to at least look at stdin for input but opens /dev/tty for output.
This makes it inordinatly difficult to drive from a script or pipe the output
to something else as compared to copying the stdin/stdout descriptors...

-- 
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)