Admin logging SoC project requirements

[Gerald (Jerry) Carter]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Michael,

Here are some of the requirements I'd like to discuss
regarding the admin logging.   The logging should
help an admin achieve three things IMO

1. monitor activity the system
2. audit changes to the system
3. warn of potential problems and possibly advise
   on how to correct them

I believe that the system should

* Utilize syslog
* Provide filters in smb.conf for which subsystems
  will log events (printing, account management,
  authentication, share management, etc...)
* Have a defined set of IDs for events
* Have a defined format string for easy parsing

The long term maintenance and usability of the system
will rest upon some control over developers as to what
is logged.  A noisy log starts us back down the Samba's
own debug logs.

How does this sound to you?






cheers,jerry
=====================================================================
Samba                                    ------- http://www.samba.org
Centeris                         -----------  http://www.centeris.com
"What man is a man who does not make the world better?"      --Balian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iD8DBQFEeKJFIR7qMdg1EfYRAumTAJ9/uKPjZNLQYmZAwDH+VhaUuJw5bACfUvPz
Cz81gWoaIfAWsSBf4ums/28=
=4eP/
-----END PGP SIGNATURE-----