On 10/12/98 11:11:44 you wrote:
In our environment, any logging that netapp can provide is probably useful to us in some way or another. For CIFS, the timestamp, loginid, and hostname or IP address of the login would be invaluable.
All of your resonings are fine, but as I pointed out, you don't really have this information for NFS access either, except to the extent that a UNIX server records a login (but wouldn't if from a PC). So I don't think you should be picking on CIFS on the filer! As I said, running NT security with a PDC would track this information for you. However, having the filer log CIFS and PC-NFS authentications would be useful.
If "cifs sessions" can print the active CIFS sessions, then how difficult could it possibly be to log when these sessions begin and end?
I'm picking on CIFS because each user has an individual session, with an identifiable beginning and end. NFS works totally differently, but we can at least get the info we need from unix logs. A lot of our students have their own PCs in their dorm rooms, so we have no access to these PCs. NT security is not an option for use because we have almost 20,000 accounts now and will eventually have almost 30,000. I haven't calculated what the license fee is for 30,000 users on a NT server. We are using the same NIS maps for our unix servers as for CIFS logins on the netapp. It's real handy for account administration and users have the same password (and same home directory) for both services.
Steve Losen scl@virginia.edu phone: 804-924-0640
University of Virginia ITC Unix Support