Hey Guys, Clayton is out of town for a little while but I think I may be able to answer some of these questions.
There are no longer two different branches, Clayton's changes have been merged back into HEAD (trunk), and we're all working out of the same repository. I'm not too familiar with the logrotate.php stuff for the new code as I haven't yet tried it myself, so I have no idea what is working or what is not. As for not making it into the latest build, I don't think anyone should be surprised 8). What we really need to do and I think Claus is onboard with this, is make a 'stable' branch or tag off a release from 2.8.1 code, and create a seperate branch for the bleeding edge stuff we're working on and call it un-stable. -----Original Message----- From: [EMAIL PROTECTED] on behalf of Vadim Pushkin Sent: Mon 7/17/2006 8:07 AM To: [EMAIL PROTECTED]; [email protected] Cc: [EMAIL PROTECTED] Subject: Re: [Php-syslog-ng-support] Errors Upon Login, Using Latest Code Hi Joel; I remember your post, in fact I had asked for a copy as an attachment :) I had seen a post by Clayton that he had a new logrotate.php, which fixed some issues with that function. The bigger problem here is why it was not properly added into the latest build, and what else was potentially left out? This is a big problem since all rollouts must have as tight a build as possible. Clayton, is there a reason for the non-change to logrotate.php? Lastly, I applaud Clayton for all of his efforts in helping to maintain the project, but does anyone know what Claus' involvement is now? Are there two or more branches to this project? Thanks all, .vp >From: Joel <[EMAIL PROTECTED]> >Reply-To: Joel <[EMAIL PROTECTED]> >To: Vadim Pushkin ><[EMAIL PROTECTED]>,[email protected] >CC: [EMAIL PROTECTED] >Subject: Re: [Php-syslog-ng-support] Errors Upon Login, Using Latest Code >Well, if it's never been touched there was an error in logrotate.. but I >was hoping one of guys had corrected. > >I would say to search the archives.. but .. here it is, I'll repost. In >this logrotate you'll note that there is one code section that I >duplicated. > > The logrotate snippet that drops the old logs is right before the snippet >to create the >merge table. The array that feeds both is not updated between. I'll paste >my updated >logrotate in below, but I've hacked my logrotate to heck in order to figure >everything out. > >Anyway, this version uses logsDATE and is meant to run ahead of time, >creating each days log file just prior to use. (I run mine at 23:55) This >way the log files never get renamed, it just seems to be a really clean way >to do it. > >-------------------------- > > I think I've found the root cause for the issue with logrotate in the 2.8 >code. [...SNIP...] ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Php-syslog-ng-support mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/php-syslog-ng-support ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Php-syslog-ng-support mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/php-syslog-ng-support
