home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!charon.amdahl.com!amdahl!rtech!pacbell.com!ames!haven.umd.edu!mimsy!nmrdc1!frmug!cpio1!bernard
- From: bernard@cpio1.fr.mugnet.org (Bernard Fouche)
- Newsgroups: comp.unix.wizards
- Subject: How to avoid calling time(2)
- Message-ID: <1993Jan27.195309.15120@cpio1.fr.mugnet.org>
- Date: 27 Jan 93 19:53:09 GMT
- Sender: bernard@cpio1.fr.mugnet.org (Bernard Fouche)
- Organization: CPIO S.A.
- Lines: 29
-
-
- Hi wizards!
-
- I run many applications that need to call very often the time(2)
- system call. I do not see how I could design my programs to do without
- having to get the result of time(2) very ofen.
-
- But I wonder if there is a way (on a 486 running Dell Unix 2.0 at
- least) to get time information without having to do a system call each
- time.
-
- For instance, does someone know if I can get a pointer toward the
- value of time that is stored somewhere in the system ? Of course this
- should work with processes having no suid bit set nor running as root
- and files like /unix or /dev/kmem must stay to be not readable by
- anyone :-)
-
- Or am I going the wrong way because the time(2) system call is so
- light that I should try to find other means to reduce the impact of my
- applications on the system ?
-
- Any comment or hint welcome !
-
- Thank you !
- --
- --------------------------------------------------------------------------
- Bernard Fouche VOX : +(33) (1) 48.04.56.30 FAX : (33) (1) 48.04.98.95
- Email : bernard@cpio1.fr.mugnet.org
- Postal Mail : CPIO S.A., 13-15 Rue de la Verrerie, 75004 Paris, France
-