Xref: utzoo comp.unix.wizards:10920 comp.os.misc:497
Path: utzoo!utgpu!attcan!uunet!tektronix!reed!psu-cs!qiclab!bigtex!james
From: james@bigtex.uucp (James Van Artsdalen)
Newsgroups: comp.unix.wizards,comp.os.misc
Subject: Re: tracing system calls
Message-ID: <7460@bigtex.uucp>
Date: 3 Sep 88 06:29:36 GMT
References: <21606@ccicpg.UUCP> <7622@boring.cwi.nl> <2040@cuuxb.ATT.COM> <66624@sun.uucp>
Reply-To: james@bigtex.UUCP (James Van Artsdalen)
Organization: F.B.N. Software, Austin TX
Lines: 20

In article <66624@sun.uucp>, brent%terra@Sun.COM (Brent Callaghan) wrote:

> And how!  Actually any SunOs 4.0 user can do that now with
> the trace(1) command.

> 	$ trace date

I count 8 closes, 6 mmaps, 5 opens, 3 reads, 2 munmaps, 1 write...

What on earth does all of this have to do with printing the date and
time???  getgid?  ioctl?  That's 36 system calls.

I don't want to flame Sun over trace though: that is incredibly
useful.  I am curious about implementation though: if it will display
the data for write(2) it would seem a security hole unless disabled
for suid processes.  Is there any possible way to write a similar
program under SysVr3 without kernel modifications?
-- 
James R. Van Artsdalen    ...!uunet!utastro!bigtex!james     "Live Free or Die"
Home: 512-346-2444 Work: 328-0282; 110 Wild Basin Rd. Ste #230, Austin TX 78746