Finally, starting tommorow evening (if we’re lucky the new server will be ready by this time), pinetd2 will go in production mode on ooKoo.org
This is a big step toward debugging, and will help me to kill most existing but yet unknown bugs in pinetd2.
Remember that pinetd2 is multicompatible. When updating, tables structures will be updated, but if downgrading they will be reverted to their original state.
As you may know, I’m currently rewritting the whole pinetd project to a new project called pinetd2.
Right now, we finally have partially reached the functionnality level of pinetd (being able to receive mails, and check them with pop), and now IMAP4 is also working (you can receive mails via imap, but not yet search and do nice stuff imap allows).
pinetd2 is still missing a MTA (this should be a matter of days) and more imap4rev1 functions (this is a matter of one or two weeks). Once this is done and once PHP 5.3 is released, pinetd will be officially OBSOLETE, and pinetd2 will become the new officially supported version. Please note that extra attention has been ported to make pinetd2 compatible with pinetd, without even having to run an update tool. Just extract pinetd2 to a new directory, copy your config file from pinetd, and run it. Your config file will merged in the XML config used by pinetd2, and you’ll have to check it a last time before running the daemon for real.
Pinetd on ohloh results in something like that :
If you didn’t hear before about pinetd, let me tell you more about it.
Initially, when PHP3 was out, I wrote a mail server using php. It was initially using xinetd to be run, then PHP/NC was born. PHP/NC (NC = Non-Connu) was a normal build of php 3, including a few more functions about sockets manipulation. It wasn’t really safe, but allowed more control over sockets in php.
Then, PHP4 was released, and a socket extensions was there too…