Manually change the permissions for syslog on your local machine, make the test fail, change the permissions to be correct and make sure the test succeeds. Maybe log something then strpos the contents of tail. That's all you can really do. -Matt
On Sat, Sep 20, 2008 at 2:48 AM, Thomas Gelf <[EMAIL PROTECTED]> wrote: > Matthew Weier O'Phinney schrieb: > >> "Ready for Review" means that you're ready to receive community >> feedback; it's up to you to make that decision. We ask that you have >> community review for at least a week prior to then re-parenting it to >> the 'Ready for Recommendation' area -- which is when the Zend internal >> team will review it and decide whether to include it, and where. >> > > Ok, so I'm ready for feedback right now ;-) > > Edit the page. Below the area where you add content, there's a tree -- >> simply drag your page's entry to the appropriate section, and then save >> the page. >> > > Thank you, wouldn't have found that without your help! > > What about unit tests, do I have to provide them too? And specific for > my proposal: any idea how the tests should look like? There are just > three simple functions, shutdown() will and should never fail, the > constructor and _write are failing when syslog itself has gone away. > > I could achieve this by removing or changing permissions on /dev/log, > no idea about Windows. But I've some doubt if doing so would make > people running the tests happy :p > > Regards, > Thomas > >
