We like to keep track of when our users login to CIFS so we use

options cifs.trace_login on

but under 7.0.1R1 this is extremely chatty.

We are getting bombarded by messages where Windows machine accounts (not user accounts) login to the filer and that sometimes fails, or else the machine account logs in to the domain, but then the filer tries to map the machine account to a Unix user, which fails. Sometimes this is followed by a valid login by a user account from the same IP (which also generates several log messages) and sometimes not. But most of the noise seems to be caused by Windows machine accounts.

It's Thursday afternoon and our /etc/messages file is 260M. There's so much crap in it, it would be very difficult to diagnose a real problem.

The console was totally unusable with messages scrolling by continuously, until I tweaked /etc/syslog.conf. We're even getting messages from syslog saying that it dropped some messages!

I tried options cifs.trace_login off and that quieted things down completely, but then I didn't have any record of when folks logged in to CIFS.

I suppose I can muck some more with syslog.conf. Any other suggestions?

Steve Losen scl@virginia.edu phone: 434-924-0640

University of Virginia ITC Unix Support