| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |
Message-Id: <4.3.2.7.2.20010626094306.00ab1430@psdt.com> Date: Tue, 26 Jun 2001 09:46:52 -0700 To: info-afs@transarc.com From: Peter Scott <Peter.J.Scott@jpl.nasa.gov> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed It's vexing, if not impossible, to try and track down how some unexpected filesystem change came about: why is this PTS group gone, who removed this volume, etc. We would like to have logging of all commands requiring admin tokens if not all fs/vos/pts/kas. Yes, we could wrap them all, although that's no guarantee, and it doesn't help with third-party applications that are linked into the appropriate APIs. The right place to do this is on the server. I reckon the answer is, "Go ahead and hack that into OpenAFS if you want it," but does anyone have anything else to add? -- Peter Scott Peter.J.Scott@jpl.nasa.gov
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |