Project description and timeline

Develop an Administrative Logging System (Samba 3)

Project description as by Samba Website:

"The log files in Samba are commonly of more use to developers than to administrators. A new logging system (in parallel with the existing debug logs) similar to the Windows auditing facilities would record those specific events of concern to sysadmins. This support would include auditing for printers, users & groups, configuration changes, etc..."

Proposed Timeline

May 23, 2006--June 7, 2006
Begin of project
Understanding Samba architecture, finding modules etc. to which to connect own code, understanding existing logging structure. Comparison with other Operating Systems' logging systems.
June 8, 2006--June 14, 2006
Designing new logging system, deciding upon exact features (i.e. which events to log, what to configure)
June 15, 2006--June 26, 2006
First implementation of a sample logging for one facility (probably file access)
Finished till mid-term evaluation (June 26); as such the time needed by the mentor to look into code produced by me is reduced
July 1, 2006--July 15, 2006
Building logging system -- configuration options, logging output etc. Assure cooperation with first implementation from previous step
July 16, 2006--August 5, 2006
Implementing logging for other items as specified above
August 6, 2006--August 12, 2006
Test system. (Perhaps inclusion into automated test system?)
Write user/admin documentation (apart from the as always well documented source code).
August 13, 2006--August 21, 2006
Spare time in case of delay.
August 21, 2006
End of project

A similarly timeline could be applied to a second project I find interesting: Subversion VFS Module (Samba 3). Meanwhile, I prefer the described project because I can very clearly see its use.


Michael Krax
Last modified: Sat May 6 18:59:53 CEST 2006