home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!pipex!doc.ic.ac.uk!uknet!axion!rtf.bt.co.uk!traub
- From: traub@rtf.bt.co.uk (Michael Traub)
- Newsgroups: biz.sco.general
- Subject: Re: time command
- Message-ID: <1992Dec31.083400.2180@rtf.bt.co.uk>
- Date: 31 Dec 92 08:34:00 GMT
- References: <C03p7q.9v1@world.std.com>
- Organization: BT Customer Systems, Brighton, UK
- Lines: 14
-
- In article <C03p7q.9v1@world.std.com> apl@world.std.com (Anthony P Lawrence) writes:
- >The only rational explanation is that either the multiport card or the
- >terminal (or both) are doing a lot of buffering so that 'time' thinks
- >the command is complete when it actually isn't.
-
- We came across this problem with a driver we wrote. The solution was to
- write a small program which outputs loads of text (the equivalent of
- your "ls") *then* read the cursor position back from the terminal (assuming
- your terminal has this feature). The elapsed time then reflected reality.
-
-
- --
- Michael Traub
- BT Customer Systems, Brighton Systems Centre. traub@btcs.bt.co.uk
-