Hey all, I'm preparing to start development of a new version of 'smbstatus' that produces XML output, instead of the tabular data it currently produces. This follows an attempt to parse the output of the current 'smbstatus' ( 3.0.22) using grep and a few other shell tools, from a system call in PHP, and then further RegEx parsing to create a multidimensional array of the 'smbstatus'. After using the shell tools and PHP to handle this information for a few months, I've become dissatisfied with the inefficiency and burden this puts on the CPU. The idea is that I can make a system call to this 'smbstatusxml' program (written in a compiled language such as C++) to pull the information directly from the samba libraries directly into XML. I believe this will be far more efficient, and a whole lot faster, since then I can load the information into an XML parser in PHP and then format it into tables, etc; or I could just pull it directly through PHP as XML and display it via some other means (RSS feed?). I've started a SourceForge project at http://sourceforge.net/projects/smbstatusxml ... though at this time I have no significant experience with CVS or development in a SourceForge context, so I've got some learning to do before I proceed in this manner. I wonder if it would be better to start development of this tool in the existing Samba CVS, but of course need authorization from existing project leaders before that would happen, and that depends on what value they see in this type of tool. I'd like other people's thoughts and opinions on this. Thanks and Regards, -- _______________________ sb "Infinite loops... yeah... those take somewhat longer than average."
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Samuel Briesemeister wrote:> Hey all, > > I'm preparing to start development of a new version of > 'smbstatus' that produces XML output, instead of the tabular > data it currently produces....> I've started a SourceForge project at > http://sourceforge.net/projects/smbstatusxml ... though at > this time I have no significant experience with CVS or development > in a SourceForge context, so I've got some learning to do > before I proceed in this manner. I wonder if it would be better > to start development of this tool in the existing Samba > CVS, but of course need authorization from existing project > leaders before that would happen, and that depends > on what value they see in this type of tool. > > I'd like other people's thoughts and opinions on this.XML output would be added to the current smbstatus tool using --output={text,xml}. That's one possibility. I don't really think such a tool could exist outside of the Samba code base since it would ideally need to access Samba's tdb files directly which would mean keeping up with internal format changes as well. People without write access to the Samba svn code base can use Bazaar-NG for development (or anonymous svn if you really have to). See http://bazaar-vcs.org/ for details on bzr. You can branch using the svn bzr plugin or branch from http://www.samba.org/~jerry/bzr/SAMBA_3_0.bzr When you have code that is ready to be reviewed, post to the samba-technical list. 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.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFh2EDIR7qMdg1EfYRAsKaAKDa/u7ZmB9N38pizoe5FCKPHnqQuwCcCWuo Up1maMhZISaG067O/AgjMaU=CcYA -----END PGP SIGNATURE-----