From pvrabec at redhat.com Fri May 2 11:31:13 2008 From: pvrabec at redhat.com (Peter Vrabec) Date: Fri, 2 May 2008 11:31:13 +0200 Subject: [phpLogCon] phplogcon-2.1.3 Message-ID: <200805021131.13085.pvrabec@redhat.com> Hi folks, thnx. for phplogcon, v2.1.3 works fine. I have submitted review request for inclusion in Fedora. https://bugzilla.redhat.com/show_bug.cgi?id=444722. From pvrabec at redhat.com Fri May 2 11:17:15 2008 From: pvrabec at redhat.com (Peter Vrabec) Date: Fri, 2 May 2008 11:17:15 +0200 Subject: [phpLogCon] phplogcon-2.1.3 Message-ID: <200805021117.15997.pvrabec@redhat.com> Hi folks, thnx. for phplogcon, v2.1.3 works fine. I have submitted review request for inclusion in Fedora. https://bugzilla.redhat.com/show_bug.cgi?id=444722. From friedl at hq.adiscon.com Fri May 2 16:19:46 2008 From: friedl at hq.adiscon.com (Florian Riedl) Date: Fri, 2 May 2008 16:19:46 +0200 Subject: [phpLogCon] phpLogCon 2.3.0 released Message-ID: <577465F99B41C842AAFBE9ED71E70ABA308F37@grfint2.intern.adiscon.com> Hi all, we have released phpLogCon 2.3.0, the first release of a new feature-enriched development branch. Version's 2.1.x are now on the beta branch and set to stabilize over the next few weeks (in short, this means they will receive bug fixes, but no new features). Version 2.3.0 provides changed database drivers with much better performance, especially for large databases. It also features new context-sensitive popup menus, which enable to quickly filter on some items. These menus are an important new technology that will be utilized in the future for enhanced troubleshooting capabilities. Download: http://www.phplogcon.org/Downloads-req-viewdownloaddetails-lid-11.phtml Florian Riedl From rgerhards at hq.adiscon.com Sat May 3 11:11:15 2008 From: rgerhards at hq.adiscon.com (Rainer Gerhards) Date: Sat, 3 May 2008 11:11:15 +0200 Subject: [phpLogCon] phpLogCon 2.3.1 released Message-ID: <577465F99B41C842AAFBE9ED71E70ABA308F3C@grfint2.intern.adiscon.com> Hi all, we have released version 2.3.1 of phpLogCon. This version provides an auto-reload functionality (automatic tail of logfiles), adds support for http gzip compression and improved the page title. This is a recommended update for all development branch users. Details and Download: http://www.phplogcon.org/downloads We hoipe this release is useful. As always, feedback is appreciated. Rainer From pvrabec at redhat.com Wed May 14 16:25:01 2008 From: pvrabec at redhat.com (Peter Vrabec) Date: Wed, 14 May 2008 16:25:01 +0200 Subject: [phpLogCon] install.php remove or not Message-ID: <200805141625.01176.pvrabec@redhat.com> Hi folks, I have a Q. for you. It's suggested that install.php should be removed after configuration. Is this behavior OK? What if someone want to do another configuration? When you done the configuration, removed install.php and do the package update. Should or shouldn't be install.php installed? I thing it shouldn't, but we need to handle this problem inside rpm. From alorbach at ro1.adiscon.com Thu May 15 10:31:52 2008 From: alorbach at ro1.adiscon.com (Andre Lorbach) Date: Thu, 15 May 2008 10:31:52 +0200 Subject: [phpLogCon] install.php remove or not In-Reply-To: <200805141625.01176.pvrabec@redhat.com> References: <200805141625.01176.pvrabec@redhat.com> Message-ID: Hi, these are good questions ;). The behavior is wanted, the install.php script needs to be removed/renamed after installation, otherwise it would be possible to overwrite the users config.php by running the installation again. The user will be able to set options within phpLogCon at some point in future versions. When the package is updated, install.php should not be installed. If there is an update needed in future, phpLogCon will handle it with an update script. -- I hope this helps - best regards, Andre Lorbach > -----Original Message----- > From: phplogcon-bounces at lists.adiscon.com [mailto:phplogcon- > bounces at lists.adiscon.com] On Behalf Of Peter Vrabec > Sent: Wednesday, May 14, 2008 4:25 PM > To: phplogcon at lists.adiscon.com > Subject: [phpLogCon] install.php remove or not > > Hi folks, > > I have a Q. for you. > > It's suggested that install.php should be removed after configuration. Is this > behavior OK? What if someone want to do another configuration? > > When you done the configuration, removed install.php and do the package > update. Should or shouldn't be install.php installed? I thing it shouldn't, > but we need to handle this problem inside rpm. > _______________________________________________ > phpLogCon mailing list > http://lists.adiscon.net/mailman/listinfo/phplogcon From pvrabec at redhat.com Thu May 15 14:37:46 2008 From: pvrabec at redhat.com (Peter Vrabec) Date: Thu, 15 May 2008 14:37:46 +0200 Subject: [phpLogCon] install.php remove or not In-Reply-To: References: <200805141625.01176.pvrabec@redhat.com> Message-ID: <200805151437.46121.pvrabec@redhat.com> Hi, On Thursday 15 May 2008 10:31:52 am Andre Lorbach wrote: > Hi, > > these are good questions ;). > > The behavior is wanted, the install.php script needs to be > removed/renamed after installation, otherwise it would be possible to > overwrite the users config.php by running the installation again. I think we can control access via apache configuration. install.php allowed only from localhost. > The > user will be able to set options within phpLogCon at some point in > future versions. What do you mean "set options"? Edit config file? > When the package is updated, install.php should not be installed. This won't be problem. > If > there is an update needed in future, phpLogCon will handle it with an > update script. Could you explain it little more. > -- > I hope this helps - best regards, > Andre Lorbach > > > -----Original Message----- > > From: phplogcon-bounces at lists.adiscon.com [mailto:phplogcon- > > bounces at lists.adiscon.com] On Behalf Of Peter Vrabec > > Sent: Wednesday, May 14, 2008 4:25 PM > > To: phplogcon at lists.adiscon.com > > Subject: [phpLogCon] install.php remove or not > > > > Hi folks, > > > > I have a Q. for you. > > > > It's suggested that install.php should be removed after configuration. > > Is this > > > behavior OK? What if someone want to do another configuration? > > > > When you done the configuration, removed install.php and do the > > package > > > update. Should or shouldn't be install.php installed? I thing it > > shouldn't, > > > but we need to handle this problem inside rpm. > > _______________________________________________ > > phpLogCon mailing list > > http://lists.adiscon.net/mailman/listinfo/phplogcon > > _______________________________________________ > phpLogCon mailing list > http://lists.adiscon.net/mailman/listinfo/phplogcon From alorbach at ro1.adiscon.com Thu May 15 14:48:49 2008 From: alorbach at ro1.adiscon.com (Andre Lorbach) Date: Thu, 15 May 2008 14:48:49 +0200 Subject: [phpLogCon] install.php remove or not In-Reply-To: <200805151437.46121.pvrabec@redhat.com> References: <200805141625.01176.pvrabec@redhat.com> <200805151437.46121.pvrabec@redhat.com> Message-ID: > -----Original Message----- > From: phplogcon-bounces at lists.adiscon.com [mailto:phplogcon- > bounces at lists.adiscon.com] On Behalf Of Peter Vrabec > Sent: Thursday, May 15, 2008 2:38 PM > To: phplogcon at lists.adiscon.com > Subject: Re: [phpLogCon] install.php remove or not > > Hi, > > On Thursday 15 May 2008 10:31:52 am Andre Lorbach wrote: > > Hi, > > > > these are good questions ;). > > > > The behavior is wanted, the install.php script needs to be > > removed/renamed after installation, otherwise it would be possible to > > overwrite the users config.php by running the installation again. > I think we can control access via apache configuration. install.php allowed > only from localhost. > > > The > > user will be able to set options within phpLogCon at some point in > > future versions. > What do you mean "set options"? Edit config file? Yes once we have a user management system implemented, which can be turned on and off optionally, the user will be able to configure all the options within phpLogCon user interface. > > When the package is updated, install.php should not be installed. > This won't be problem. > > > If > > there is an update needed in future, phpLogCon will handle it with an > > update script. > Could you explain it little more. There will be some kind of update.php which can only be access by authorized users (requires the user management system) which will detect and perform necessary updates. The details have not been worked out yet, but this is how is going to work. Best regards, Andre Lorbach From pvrabec at redhat.com Thu May 15 14:57:25 2008 From: pvrabec at redhat.com (Peter Vrabec) Date: Thu, 15 May 2008 14:57:25 +0200 Subject: [phpLogCon] install.php remove or not In-Reply-To: References: <200805141625.01176.pvrabec@redhat.com> <200805151437.46121.pvrabec@redhat.com> Message-ID: <200805151457.25616.pvrabec@redhat.com> ok. thnx. for answers Andre :) I'll do following: * suggest users to rename config.php to something safe * do not install install.php during package UPDATE * restrict access to phplogcon, allowed only from localhost by default On Thursday 15 May 2008 02:48:49 pm Andre Lorbach wrote: > > -----Original Message----- > > From: phplogcon-bounces at lists.adiscon.com [mailto:phplogcon- > > bounces at lists.adiscon.com] On Behalf Of Peter Vrabec > > Sent: Thursday, May 15, 2008 2:38 PM > > To: phplogcon at lists.adiscon.com > > Subject: Re: [phpLogCon] install.php remove or not > > > > Hi, > > > > On Thursday 15 May 2008 10:31:52 am Andre Lorbach wrote: > > > Hi, > > > > > > these are good questions ;). > > > > > > The behavior is wanted, the install.php script needs to be > > > removed/renamed after installation, otherwise it would be possible > > to > > > > overwrite the users config.php by running the installation again. > > > > I think we can control access via apache configuration. install.php > > allowed > > > only from localhost. > > > > > The > > > user will be able to set options within phpLogCon at some point in > > > future versions. > > > > What do you mean "set options"? Edit config file? > > Yes once we have a user management system implemented, which can be > turned on and off optionally, the user will be able to configure all the > options within phpLogCon user interface. > > > > When the package is updated, install.php should not be installed. > > > > This won't be problem. > > > > > If > > > there is an update needed in future, phpLogCon will handle it with > > an > > > > update script. > > > > Could you explain it little more. > > There will be some kind of update.php which can only be access by > authorized users (requires the user management system) which will detect > and perform necessary updates. The details have not been worked out yet, > but this is how is going to work. > > Best regards, > Andre Lorbach > > > > > > _______________________________________________ > phpLogCon mailing list > http://lists.adiscon.net/mailman/listinfo/phplogcon From alorbach at ro1.adiscon.com Thu May 15 15:04:57 2008 From: alorbach at ro1.adiscon.com (Andre Lorbach) Date: Thu, 15 May 2008 15:04:57 +0200 Subject: [phpLogCon] install.php remove or not In-Reply-To: <200805151457.25616.pvrabec@redhat.com> References: <200805141625.01176.pvrabec@redhat.com><200805151437.46121.pvrabec@redhat.com> <200805151457.25616.pvrabec@redhat.com> Message-ID: > -----Original Message----- > From: phplogcon-bounces at lists.adiscon.com [mailto:phplogcon- > bounces at lists.adiscon.com] On Behalf Of Peter Vrabec > Sent: Thursday, May 15, 2008 2:57 PM > To: phplogcon at lists.adiscon.com > Subject: Re: [phpLogCon] install.php remove or not > > ok. thnx. for answers Andre :) > > I'll do following: > * suggest users to rename config.php to something safe > * do not install install.php during package UPDATE > * restrict access to phplogcon, allowed only from localhost by default Sounds good to me :) Regarding the config.php, the default template is stored in the include directory called "config.sample.php". The config.php is created out of this template during the installation only. So you can savely copy all files over the old except for the install.php. Best regards, Andre Lorbach From pvrabec at redhat.com Fri May 16 15:22:14 2008 From: pvrabec at redhat.com (Peter Vrabec) Date: Fri, 16 May 2008 15:22:14 +0200 Subject: [phpLogCon] install.php remove or not In-Reply-To: References: <200805141625.01176.pvrabec@redhat.com> <200805151457.25616.pvrabec@redhat.com> Message-ID: <200805161522.15072.pvrabec@redhat.com> On Thursday 15 May 2008 03:04:57 pm Andre Lorbach wrote: > > -----Original Message----- > > From: phplogcon-bounces at lists.adiscon.com [mailto:phplogcon- > > bounces at lists.adiscon.com] On Behalf Of Peter Vrabec > > Sent: Thursday, May 15, 2008 2:57 PM > > To: phplogcon at lists.adiscon.com > > Subject: Re: [phpLogCon] install.php remove or not > > > > ok. thnx. for answers Andre :) > > > > I'll do following: > > * suggest users to rename config.php to something safe > > * do not install install.php during package UPDATE > > * restrict access to phplogcon, allowed only from localhost by default > > Sounds good to me :) > > Regarding the config.php, the default template is stored in the include > directory called "config.sample.php". The config.php is created out of > this template during the installation only. So you can savely copy all > files over the old except for the install.php. Ooops. Things around install.php are not going well. see: https://bugzilla.redhat.com/show_bug.cgi?id=444722 $ rpm -V phplogcon S.5....T c /etc/phplogcon/config.php missing /usr/share/phplogcon/install.php Do you think it would be possible to handle this problem different way? For example in install.php something like: if configured then { exit } else { do usual } > Best regards, > Andre Lorbach > _______________________________________________ > phpLogCon mailing list > http://lists.adiscon.net/mailman/listinfo/phplogcon From rgerhards at hq.adiscon.com Fri May 16 15:37:36 2008 From: rgerhards at hq.adiscon.com (Rainer Gerhards) Date: Fri, 16 May 2008 15:37:36 +0200 Subject: [phpLogCon] install.php remove or not In-Reply-To: <200805161522.15072.pvrabec@redhat.com> References: <200805141625.01176.pvrabec@redhat.com> <200805151457.25616.pvrabec@redhat.com> <200805161522.15072.pvrabec@redhat.com> Message-ID: <1210945056.22738.508.camel@localhost.localdomain> Hi Peter, I just talked with Andre. He told me that he is doing the same thing as e.g. phpBB. I think there is a RPM available for phpBB. Could you have a look at that RPM and tell us the difference? We could probably implement it along those lines... Rainer On Fri, 2008-05-16 at 15:22 +0200, Peter Vrabec wrote: > On Thursday 15 May 2008 03:04:57 pm Andre Lorbach wrote: > > > -----Original Message----- > > > From: phplogcon-bounces at lists.adiscon.com [mailto:phplogcon- > > > bounces at lists.adiscon.com] On Behalf Of Peter Vrabec > > > Sent: Thursday, May 15, 2008 2:57 PM > > > To: phplogcon at lists.adiscon.com > > > Subject: Re: [phpLogCon] install.php remove or not > > > > > > ok. thnx. for answers Andre :) > > > > > > I'll do following: > > > * suggest users to rename config.php to something safe > > > * do not install install.php during package UPDATE > > > * restrict access to phplogcon, allowed only from localhost by default > > > > Sounds good to me :) > > > > Regarding the config.php, the default template is stored in the include > > directory called "config.sample.php". The config.php is created out of > > this template during the installation only. So you can savely copy all > > files over the old except for the install.php. > > Ooops. Things around install.php are not going well. > see: https://bugzilla.redhat.com/show_bug.cgi?id=444722 > $ rpm -V phplogcon > S.5....T c /etc/phplogcon/config.php > missing /usr/share/phplogcon/install.php > > Do you think it would be possible to handle this problem different way? For > example in install.php something like: > if configured then { > exit > } > else { > do usual > } > > > > > > Best regards, > > Andre Lorbach > > _______________________________________________ > > phpLogCon mailing list > > http://lists.adiscon.net/mailman/listinfo/phplogcon > > > _______________________________________________ > phpLogCon mailing list > http://lists.adiscon.net/mailman/listinfo/phplogcon From alorbach at ro1.adiscon.com Fri May 16 15:53:22 2008 From: alorbach at ro1.adiscon.com (Andre Lorbach) Date: Fri, 16 May 2008 15:53:22 +0200 Subject: [phpLogCon] install.php remove or not In-Reply-To: <200805161522.15072.pvrabec@redhat.com> References: <200805141625.01176.pvrabec@redhat.com><200805151457.25616.pvrabec@redhat.com> <200805161522.15072.pvrabec@redhat.com> Message-ID: Hi, we could handle the configured / installed state different if we find no other way around this problem. But if possible I would like to find an alternative solution for the problem first. The installation method in phpLogCon is similar to the method used in phpbb. There is another thing that clearly tells you if phpLogCon was already configured, if the config.php file isn't empty anymore. By default an empty one with write access is shipped, right? This config.php file is written by the installation routine at the very end. So only if the config.php file is empty, the update needs to copy the install.php file. Is it possible to handle this by the package manager? -- Best regards, Andre Lorbach > -----Original Message----- > From: phplogcon-bounces at lists.adiscon.com [mailto:phplogcon- > bounces at lists.adiscon.com] On Behalf Of Peter Vrabec > Sent: Friday, May 16, 2008 3:22 PM > To: phplogcon at lists.adiscon.com > Subject: Re: [phpLogCon] install.php remove or not > > On Thursday 15 May 2008 03:04:57 pm Andre Lorbach wrote: > > > -----Original Message----- > > > From: phplogcon-bounces at lists.adiscon.com [mailto:phplogcon- > > > bounces at lists.adiscon.com] On Behalf Of Peter Vrabec > > > Sent: Thursday, May 15, 2008 2:57 PM > > > To: phplogcon at lists.adiscon.com > > > Subject: Re: [phpLogCon] install.php remove or not > > > > > > ok. thnx. for answers Andre :) > > > > > > I'll do following: > > > * suggest users to rename config.php to something safe > > > * do not install install.php during package UPDATE > > > * restrict access to phplogcon, allowed only from localhost by default > > > > Sounds good to me :) > > > > Regarding the config.php, the default template is stored in the include > > directory called "config.sample.php". The config.php is created out of > > this template during the installation only. So you can savely copy all > > files over the old except for the install.php. > > Ooops. Things around install.php are not going well. > see: https://bugzilla.redhat.com/show_bug.cgi?id=444722 > $ rpm -V phplogcon > S.5....T c /etc/phplogcon/config.php > missing /usr/share/phplogcon/install.php > > Do you think it would be possible to handle this problem different way? For > example in install.php something like: > if configured then { > exit > } > else { > do usual > } > > > > > > Best regards, > > Andre Lorbach > > _______________________________________________ > > phpLogCon mailing list > > http://lists.adiscon.net/mailman/listinfo/phplogcon > > > _______________________________________________ > phpLogCon mailing list > http://lists.adiscon.net/mailman/listinfo/phplogcon From rgerhards at hq.adiscon.com Fri May 16 15:55:45 2008 From: rgerhards at hq.adiscon.com (Rainer Gerhards) Date: Fri, 16 May 2008 15:55:45 +0200 Subject: [phpLogCon] install.php remove or not In-Reply-To: References: <200805141625.01176.pvrabec@redhat.com> <200805151457.25616.pvrabec@redhat.com> <200805161522.15072.pvrabec@redhat.com> Message-ID: <1210946145.22738.511.camel@localhost.localdomain> If I understood the bugzilla entry correctly, the empty file causes other grief ;) So it might be good to add a comment to it (e.g. /*NOTCONFIGURED*/\n). Then, you could check that comment. Two problems solved ;) Rainer On Fri, 2008-05-16 at 15:53 +0200, Andre Lorbach wrote: > Hi, > > we could handle the configured / installed state different if we find no > other way around this problem. But if possible I would like to find an > alternative solution for the problem first. > > The installation method in phpLogCon is similar to the method used in > phpbb. > > There is another thing that clearly tells you if phpLogCon was already > configured, if the config.php file isn't empty anymore. By default an > empty one with write access is shipped, right? This config.php file is > written by the installation routine at the very end. So only if the > config.php file is empty, the update needs to copy the install.php file. > Is it possible to handle this by the package manager? > > -- > Best regards, > Andre Lorbach > > > > > -----Original Message----- > > From: phplogcon-bounces at lists.adiscon.com [mailto:phplogcon- > > bounces at lists.adiscon.com] On Behalf Of Peter Vrabec > > Sent: Friday, May 16, 2008 3:22 PM > > To: phplogcon at lists.adiscon.com > > Subject: Re: [phpLogCon] install.php remove or not > > > > On Thursday 15 May 2008 03:04:57 pm Andre Lorbach wrote: > > > > -----Original Message----- > > > > From: phplogcon-bounces at lists.adiscon.com [mailto:phplogcon- > > > > bounces at lists.adiscon.com] On Behalf Of Peter Vrabec > > > > Sent: Thursday, May 15, 2008 2:57 PM > > > > To: phplogcon at lists.adiscon.com > > > > Subject: Re: [phpLogCon] install.php remove or not > > > > > > > > ok. thnx. for answers Andre :) > > > > > > > > I'll do following: > > > > * suggest users to rename config.php to something safe > > > > * do not install install.php during package UPDATE > > > > * restrict access to phplogcon, allowed only from localhost by > default > > > > > > Sounds good to me :) > > > > > > Regarding the config.php, the default template is stored in the > include > > > directory called "config.sample.php". The config.php is created out > of > > > this template during the installation only. So you can savely copy > all > > > files over the old except for the install.php. > > > > Ooops. Things around install.php are not going well. > > see: https://bugzilla.redhat.com/show_bug.cgi?id=444722 > > $ rpm -V phplogcon > > S.5....T c /etc/phplogcon/config.php > > missing /usr/share/phplogcon/install.php > > > > Do you think it would be possible to handle this problem different > way? For > > example in install.php something like: > > if configured then { > > exit > > } > > else { > > do usual > > } > > > > > > > > > > > Best regards, > > > Andre Lorbach > > > _______________________________________________ > > > phpLogCon mailing list > > > http://lists.adiscon.net/mailman/listinfo/phplogcon > > > > > > _______________________________________________ > > phpLogCon mailing list > > http://lists.adiscon.net/mailman/listinfo/phplogcon > _______________________________________________ > phpLogCon mailing list > http://lists.adiscon.net/mailman/listinfo/phplogcon From pvrabec at redhat.com Fri May 16 16:23:21 2008 From: pvrabec at redhat.com (Peter Vrabec) Date: Fri, 16 May 2008 16:23:21 +0200 Subject: [phpLogCon] install.php remove or not In-Reply-To: <1210946145.22738.511.camel@localhost.localdomain> References: <200805141625.01176.pvrabec@redhat.com> <1210946145.22738.511.camel@localhost.localdomain> Message-ID: <200805161623.21874.pvrabec@redhat.com> quick reply On Friday 16 May 2008 03:55:45 pm Rainer Gerhards wrote: > If I understood the bugzilla entry correctly, the empty file causes > other grief ;) > > So it might be good to add a comment to it (e.g. /*NOTCONFIGURED*/\n). > Then, you could check that comment. Two problems solved ;) I agree /*NOTCONFIGURED*/\n is good idea. > Rainer > > On Fri, 2008-05-16 at 15:53 +0200, Andre Lorbach wrote: > > Hi, > > > > we could handle the configured / installed state different if we find no > > other way around this problem. But if possible I would like to find an > > alternative solution for the problem first. > > > > The installation method in phpLogCon is similar to the method used in > > phpbb. Let me see. I can't find phpBB. :( > > There is another thing that clearly tells you if phpLogCon was already > > configured, if the config.php file isn't empty anymore. By default an > > empty one with write access is shipped, right? This config.php file is > > written by the installation routine at the very end. So only if the > > config.php file is empty, the update needs to copy the install.php file. > > Is it possible to handle this by the package manager? I'm afraid it's not possible. I can only remove the file if it was an update. But then there is rpm -V problem. From alorbach at ro1.adiscon.com Fri May 16 16:44:59 2008 From: alorbach at ro1.adiscon.com (Andre Lorbach) Date: Fri, 16 May 2008 16:44:59 +0200 Subject: [phpLogCon] install.php remove or not In-Reply-To: <200805161623.21874.pvrabec@redhat.com> References: <200805141625.01176.pvrabec@redhat.com><1210946145.22738.511.camel@localhost.localdomain> <200805161623.21874.pvrabec@redhat.com> Message-ID: > On Friday 16 May 2008 03:55:45 pm Rainer Gerhards wrote: > > If I understood the bugzilla entry correctly, the empty file causes > > other grief ;) > > > > So it might be good to add a comment to it (e.g. /*NOTCONFIGURED*/\n). > > Then, you could check that comment. Two problems solved ;) > I agree /*NOTCONFIGURED*/\n is good idea. > > > Rainer > > > > On Fri, 2008-05-16 at 15:53 +0200, Andre Lorbach wrote: > > > Hi, > > > > > > we could handle the configured / installed state different if we find no > > > other way around this problem. But if possible I would like to find an > > > alternative solution for the problem first. > > > > > > The installation method in phpLogCon is similar to the method used in > > > phpbb. > Let me see. I can't find phpBB. :( > > > > There is another thing that clearly tells you if phpLogCon was already > > > configured, if the config.php file isn't empty anymore. By default an > > > empty one with write access is shipped, right? This config.php file is > > > written by the installation routine at the very end. So only if the > > > config.php file is empty, the update needs to copy the install.php file. > > > Is it possible to handle this by the package manager? > I'm afraid it's not possible. I can only remove the file if it was an update. > But then there is rpm -V problem. Ok what I can do is, I can add a check like I described above. If the config.php is empty, this means install.php is allowed to run. If the size of config.php is more then 0, the install.php script will deny any attempt to open it. In order to reconfigure phpLogCon, the config.php file would need to be deleted or replaced with an empty one. -- Best regards, Andre Lorbach From pvrabec at redhat.com Fri May 16 16:55:25 2008 From: pvrabec at redhat.com (Peter Vrabec) Date: Fri, 16 May 2008 16:55:25 +0200 Subject: [phpLogCon] install.php remove or not In-Reply-To: References: <200805141625.01176.pvrabec@redhat.com> <200805161623.21874.pvrabec@redhat.com> Message-ID: <200805161655.25421.pvrabec@redhat.com> On Friday 16 May 2008 04:44:59 pm Andre Lorbach wrote: > > On Friday 16 May 2008 03:55:45 pm Rainer Gerhards wrote: > > > If I understood the bugzilla entry correctly, the empty file causes > > > other grief ;) > > > > > > So it might be good to add a comment to it (e.g. > > /*NOTCONFIGURED*/\n). > > > > Then, you could check that comment. Two problems solved ;) > > > > I agree /*NOTCONFIGURED*/\n is good idea. > > > > > Rainer > > > > > > On Fri, 2008-05-16 at 15:53 +0200, Andre Lorbach wrote: > > > > Hi, > > > > > > > > we could handle the configured / installed state different if we > > find no > > > > > other way around this problem. But if possible I would like to > > find an > > > > > alternative solution for the problem first. > > > > > > > > The installation method in phpLogCon is similar to the method used > > in > > > > > phpbb. > > > > Let me see. I can't find phpBB. :( > > > > > > There is another thing that clearly tells you if phpLogCon was > > already > > > > > configured, if the config.php file isn't empty anymore. By default > > an > > > > > empty one with write access is shipped, right? This config.php > > file is > > > > > written by the installation routine at the very end. So only if > > the > > > > > config.php file is empty, the update needs to copy the install.php > > file. > > > > > Is it possible to handle this by the package manager? > > > > I'm afraid it's not possible. I can only remove the file if it was an > > update. > > > But then there is rpm -V problem. > > Ok what I can do is, I can add a check like I described above. If the > config.php is empty, this means install.php is allowed to run. If the > size of config.php is more then 0, the install.php script will deny any > attempt to open it. In order to reconfigure phpLogCon, the config.php > file would need to be deleted or replaced with an empty one. thnx. Andre, I think this will push us further. I'm sorry I thought I can handle it in spec file, but I was wrong. I hope it helps other distros too. > Best regards, > Andre Lorbach > _______________________________________________ > phpLogCon mailing list > http://lists.adiscon.net/mailman/listinfo/phplogcon From alorbach at ro1.adiscon.com Fri May 16 16:57:10 2008 From: alorbach at ro1.adiscon.com (Andre Lorbach) Date: Fri, 16 May 2008 16:57:10 +0200 Subject: [phpLogCon] install.php remove or not In-Reply-To: <200805161655.25421.pvrabec@redhat.com> References: <200805141625.01176.pvrabec@redhat.com><200805161623.21874.pvrabec@redhat.com> <200805161655.25421.pvrabec@redhat.com> Message-ID: > I'm afraid it's not possible. I can only remove the file if it was an > > > > update. > > > > > But then there is rpm -V problem. > > > > Ok what I can do is, I can add a check like I described above. If the > > config.php is empty, this means install.php is allowed to run. If the > > size of config.php is more then 0, the install.php script will deny any > > attempt to open it. In order to reconfigure phpLogCon, the config.php > > file would need to be deleted or replaced with an empty one. > > thnx. Andre, I think this will push us further. I'm sorry I thought I can > handle it in spec file, but I was wrong. I hope it helps other distros too. No problem ;) - the more I think about this, the more I like this way to handle the install.php. -- Best regards, Andre Lorbach From alorbach at ro1.adiscon.com Mon May 19 15:40:07 2008 From: alorbach at ro1.adiscon.com (Andre Lorbach) Date: Mon, 19 May 2008 15:40:07 +0200 Subject: [phpLogCon] install.php remove or not In-Reply-To: <200805161655.25421.pvrabec@redhat.com> References: <200805141625.01176.pvrabec@redhat.com><200805161623.21874.pvrabec@redhat.com> <200805161655.25421.pvrabec@redhat.com> Message-ID: Hi again ;)! I want to inform you that I have made the changes in the current beta branch today. >From the changelog: Changed install.php handling, so it is not necessary to remove the script anymore. To avoid problems with automatic package updating, we changed the installer handling. From now, the install.php will be allowed to run only in two cases, first if the config.php file is missing, and second if the config.php file is empty. Download available from here: http://www.phplogcon.org/downloads The devel branch will be updated tomorrow. -- Best regards, Andre Lorbach > > update. > > > > > But then there is rpm -V problem. > > > > Ok what I can do is, I can add a check like I described above. If the > > config.php is empty, this means install.php is allowed to run. If the > > size of config.php is more then 0, the install.php script will deny any > > attempt to open it. In order to reconfigure phpLogCon, the config.php > > file would need to be deleted or replaced with an empty one. > > thnx. Andre, I think this will push us further. I'm sorry I thought I can > handle it in spec file, but I was wrong. I hope it helps other distros too. From alorbach at ro1.adiscon.com Tue May 20 16:59:17 2008 From: alorbach at ro1.adiscon.com (Andre Lorbach) Date: Tue, 20 May 2008 16:59:17 +0200 Subject: [phpLogCon] install.php remove or not In-Reply-To: References: <200805141625.01176.pvrabec@redhat.com><200805161623.21874.pvrabec@redhat.com><200805161655.25421.pvrabec@redhat.com> Message-ID: Hi again #2 ^^, as promised yesterday, here is the new Version from the devel branch v2.3.2, available from here: http://www.phplogcon.org/Downloads-req-viewdownloaddetails-lid-15.phtml The new version contains the install handling change from yesterday. Best regards, Andre Lorbach > -----Original Message----- > From: phplogcon-bounces at lists.adiscon.com [mailto:phplogcon- > bounces at lists.adiscon.com] On Behalf Of Andre Lorbach > Sent: Monday, May 19, 2008 3:40 PM > To: phplogcon at lists.adiscon.com > Subject: Re: [phpLogCon] install.php remove or not > > Hi again ;)! > > I want to inform you that I have made the changes in the current beta > branch today. > >From the changelog: > > Changed install.php handling, so it is not necessary to remove > the script anymore. > > To avoid problems with automatic package updating, we changed > the installer handling. > From now, the install.php will be allowed to run only in two > cases, first if the > config.php file is missing, and second if the config.php file is > empty. > > Download available from here: > http://www.phplogcon.org/downloads > > The devel branch will be updated tomorrow. > > -- > Best regards, > Andre Lorbach > > > > update. > > > > > > > But then there is rpm -V problem. > > > > > > Ok what I can do is, I can add a check like I described above. If > the > > > config.php is empty, this means install.php is allowed to run. If > the > > > size of config.php is more then 0, the install.php script will deny > any > > > attempt to open it. In order to reconfigure phpLogCon, the > config.php > > > file would need to be deleted or replaced with an empty one. > > > > thnx. Andre, I think this will push us further. I'm sorry I thought I > can > > handle it in spec file, but I was wrong. I hope it helps other distros > too. > > _______________________________________________ > phpLogCon mailing list > http://lists.adiscon.net/mailman/listinfo/phplogcon From pvrabec at redhat.com Tue May 27 10:58:44 2008 From: pvrabec at redhat.com (Peter Vrabec) Date: Tue, 27 May 2008 10:58:44 +0200 Subject: [phpLogCon] good news everyone :) Message-ID: <200805271058.44324.pvrabec@redhat.com> phplogcon passed the review finally. It was built in F9 and rawhide(F10), so I hope it will be available in fedora repositories soon. From alorbach at ro1.adiscon.com Tue May 27 11:01:19 2008 From: alorbach at ro1.adiscon.com (Andre Lorbach) Date: Tue, 27 May 2008 11:01:19 +0200 Subject: [phpLogCon] good news everyone :) In-Reply-To: <200805271058.44324.pvrabec@redhat.com> References: <200805271058.44324.pvrabec@redhat.com> Message-ID: Awesome news :) Great to hear that . Best regards, Andre Lorbach > -----Original Message----- > From: phplogcon-bounces at lists.adiscon.com [mailto:phplogcon- > bounces at lists.adiscon.com] On Behalf Of Peter Vrabec > Sent: Tuesday, May 27, 2008 10:59 AM > To: phplogcon at lists.adiscon.com > Subject: [phpLogCon] good news everyone :) > > phplogcon passed the review finally. It was built in F9 and rawhide(F10), so I > hope it will be available in fedora repositories soon. > _______________________________________________ > phpLogCon mailing list > http://lists.adiscon.net/mailman/listinfo/phplogcon From pvrabec at redhat.com Fri May 2 11:31:13 2008 From: pvrabec at redhat.com (Peter Vrabec) Date: Fri, 2 May 2008 11:31:13 +0200 Subject: [phpLogCon] phplogcon-2.1.3 Message-ID: <200805021131.13085.pvrabec@redhat.com> Hi folks, thnx. for phplogcon, v2.1.3 works fine. I have submitted review request for inclusion in Fedora. https://bugzilla.redhat.com/show_bug.cgi?id=444722. From pvrabec at redhat.com Fri May 2 11:17:15 2008 From: pvrabec at redhat.com (Peter Vrabec) Date: Fri, 2 May 2008 11:17:15 +0200 Subject: [phpLogCon] phplogcon-2.1.3 Message-ID: <200805021117.15997.pvrabec@redhat.com> Hi folks, thnx. for phplogcon, v2.1.3 works fine. I have submitted review request for inclusion in Fedora. https://bugzilla.redhat.com/show_bug.cgi?id=444722. From friedl at hq.adiscon.com Fri May 2 16:19:46 2008 From: friedl at hq.adiscon.com (Florian Riedl) Date: Fri, 2 May 2008 16:19:46 +0200 Subject: [phpLogCon] phpLogCon 2.3.0 released Message-ID: <577465F99B41C842AAFBE9ED71E70ABA308F37@grfint2.intern.adiscon.com> Hi all, we have released phpLogCon 2.3.0, the first release of a new feature-enriched development branch. Version's 2.1.x are now on the beta branch and set to stabilize over the next few weeks (in short, this means they will receive bug fixes, but no new features). Version 2.3.0 provides changed database drivers with much better performance, especially for large databases. It also features new context-sensitive popup menus, which enable to quickly filter on some items. These menus are an important new technology that will be utilized in the future for enhanced troubleshooting capabilities. Download: http://www.phplogcon.org/Downloads-req-viewdownloaddetails-lid-11.phtml Florian Riedl From rgerhards at hq.adiscon.com Sat May 3 11:11:15 2008 From: rgerhards at hq.adiscon.com (Rainer Gerhards) Date: Sat, 3 May 2008 11:11:15 +0200 Subject: [phpLogCon] phpLogCon 2.3.1 released Message-ID: <577465F99B41C842AAFBE9ED71E70ABA308F3C@grfint2.intern.adiscon.com> Hi all, we have released version 2.3.1 of phpLogCon. This version provides an auto-reload functionality (automatic tail of logfiles), adds support for http gzip compression and improved the page title. This is a recommended update for all development branch users. Details and Download: http://www.phplogcon.org/downloads We hoipe this release is useful. As always, feedback is appreciated. Rainer From pvrabec at redhat.com Wed May 14 16:25:01 2008 From: pvrabec at redhat.com (Peter Vrabec) Date: Wed, 14 May 2008 16:25:01 +0200 Subject: [phpLogCon] install.php remove or not Message-ID: <200805141625.01176.pvrabec@redhat.com> Hi folks, I have a Q. for you. It's suggested that install.php should be removed after configuration. Is this behavior OK? What if someone want to do another configuration? When you done the configuration, removed install.php and do the package update. Should or shouldn't be install.php installed? I thing it shouldn't, but we need to handle this problem inside rpm. From alorbach at ro1.adiscon.com Thu May 15 10:31:52 2008 From: alorbach at ro1.adiscon.com (Andre Lorbach) Date: Thu, 15 May 2008 10:31:52 +0200 Subject: [phpLogCon] install.php remove or not In-Reply-To: <200805141625.01176.pvrabec@redhat.com> References: <200805141625.01176.pvrabec@redhat.com> Message-ID: Hi, these are good questions ;). The behavior is wanted, the install.php script needs to be removed/renamed after installation, otherwise it would be possible to overwrite the users config.php by running the installation again. The user will be able to set options within phpLogCon at some point in future versions. When the package is updated, install.php should not be installed. If there is an update needed in future, phpLogCon will handle it with an update script. -- I hope this helps - best regards, Andre Lorbach > -----Original Message----- > From: phplogcon-bounces at lists.adiscon.com [mailto:phplogcon- > bounces at lists.adiscon.com] On Behalf Of Peter Vrabec > Sent: Wednesday, May 14, 2008 4:25 PM > To: phplogcon at lists.adiscon.com > Subject: [phpLogCon] install.php remove or not > > Hi folks, > > I have a Q. for you. > > It's suggested that install.php should be removed after configuration. Is this > behavior OK? What if someone want to do another configuration? > > When you done the configuration, removed install.php and do the package > update. Should or shouldn't be install.php installed? I thing it shouldn't, > but we need to handle this problem inside rpm. > _______________________________________________ > phpLogCon mailing list > http://lists.adiscon.net/mailman/listinfo/phplogcon From pvrabec at redhat.com Thu May 15 14:37:46 2008 From: pvrabec at redhat.com (Peter Vrabec) Date: Thu, 15 May 2008 14:37:46 +0200 Subject: [phpLogCon] install.php remove or not In-Reply-To: References: <200805141625.01176.pvrabec@redhat.com> Message-ID: <200805151437.46121.pvrabec@redhat.com> Hi, On Thursday 15 May 2008 10:31:52 am Andre Lorbach wrote: > Hi, > > these are good questions ;). > > The behavior is wanted, the install.php script needs to be > removed/renamed after installation, otherwise it would be possible to > overwrite the users config.php by running the installation again. I think we can control access via apache configuration. install.php allowed only from localhost. > The > user will be able to set options within phpLogCon at some point in > future versions. What do you mean "set options"? Edit config file? > When the package is updated, install.php should not be installed. This won't be problem. > If > there is an update needed in future, phpLogCon will handle it with an > update script. Could you explain it little more. > -- > I hope this helps - best regards, > Andre Lorbach > > > -----Original Message----- > > From: phplogcon-bounces at lists.adiscon.com [mailto:phplogcon- > > bounces at lists.adiscon.com] On Behalf Of Peter Vrabec > > Sent: Wednesday, May 14, 2008 4:25 PM > > To: phplogcon at lists.adiscon.com > > Subject: [phpLogCon] install.php remove or not > > > > Hi folks, > > > > I have a Q. for you. > > > > It's suggested that install.php should be removed after configuration. > > Is this > > > behavior OK? What if someone want to do another configuration? > > > > When you done the configuration, removed install.php and do the > > package > > > update. Should or shouldn't be install.php installed? I thing it > > shouldn't, > > > but we need to handle this problem inside rpm. > > _______________________________________________ > > phpLogCon mailing list > > http://lists.adiscon.net/mailman/listinfo/phplogcon > > _______________________________________________ > phpLogCon mailing list > http://lists.adiscon.net/mailman/listinfo/phplogcon From alorbach at ro1.adiscon.com Thu May 15 14:48:49 2008 From: alorbach at ro1.adiscon.com (Andre Lorbach) Date: Thu, 15 May 2008 14:48:49 +0200 Subject: [phpLogCon] install.php remove or not In-Reply-To: <200805151437.46121.pvrabec@redhat.com> References: <200805141625.01176.pvrabec@redhat.com> <200805151437.46121.pvrabec@redhat.com> Message-ID: > -----Original Message----- > From: phplogcon-bounces at lists.adiscon.com [mailto:phplogcon- > bounces at lists.adiscon.com] On Behalf Of Peter Vrabec > Sent: Thursday, May 15, 2008 2:38 PM > To: phplogcon at lists.adiscon.com > Subject: Re: [phpLogCon] install.php remove or not > > Hi, > > On Thursday 15 May 2008 10:31:52 am Andre Lorbach wrote: > > Hi, > > > > these are good questions ;). > > > > The behavior is wanted, the install.php script needs to be > > removed/renamed after installation, otherwise it would be possible to > > overwrite the users config.php by running the installation again. > I think we can control access via apache configuration. install.php allowed > only from localhost. > > > The > > user will be able to set options within phpLogCon at some point in > > future versions. > What do you mean "set options"? Edit config file? Yes once we have a user management system implemented, which can be turned on and off optionally, the user will be able to configure all the options within phpLogCon user interface. > > When the package is updated, install.php should not be installed. > This won't be problem. > > > If > > there is an update needed in future, phpLogCon will handle it with an > > update script. > Could you explain it little more. There will be some kind of update.php which can only be access by authorized users (requires the user management system) which will detect and perform necessary updates. The details have not been worked out yet, but this is how is going to work. Best regards, Andre Lorbach From pvrabec at redhat.com Thu May 15 14:57:25 2008 From: pvrabec at redhat.com (Peter Vrabec) Date: Thu, 15 May 2008 14:57:25 +0200 Subject: [phpLogCon] install.php remove or not In-Reply-To: References: <200805141625.01176.pvrabec@redhat.com> <200805151437.46121.pvrabec@redhat.com> Message-ID: <200805151457.25616.pvrabec@redhat.com> ok. thnx. for answers Andre :) I'll do following: * suggest users to rename config.php to something safe * do not install install.php during package UPDATE * restrict access to phplogcon, allowed only from localhost by default On Thursday 15 May 2008 02:48:49 pm Andre Lorbach wrote: > > -----Original Message----- > > From: phplogcon-bounces at lists.adiscon.com [mailto:phplogcon- > > bounces at lists.adiscon.com] On Behalf Of Peter Vrabec > > Sent: Thursday, May 15, 2008 2:38 PM > > To: phplogcon at lists.adiscon.com > > Subject: Re: [phpLogCon] install.php remove or not > > > > Hi, > > > > On Thursday 15 May 2008 10:31:52 am Andre Lorbach wrote: > > > Hi, > > > > > > these are good questions ;). > > > > > > The behavior is wanted, the install.php script needs to be > > > removed/renamed after installation, otherwise it would be possible > > to > > > > overwrite the users config.php by running the installation again. > > > > I think we can control access via apache configuration. install.php > > allowed > > > only from localhost. > > > > > The > > > user will be able to set options within phpLogCon at some point in > > > future versions. > > > > What do you mean "set options"? Edit config file? > > Yes once we have a user management system implemented, which can be > turned on and off optionally, the user will be able to configure all the > options within phpLogCon user interface. > > > > When the package is updated, install.php should not be installed. > > > > This won't be problem. > > > > > If > > > there is an update needed in future, phpLogCon will handle it with > > an > > > > update script. > > > > Could you explain it little more. > > There will be some kind of update.php which can only be access by > authorized users (requires the user management system) which will detect > and perform necessary updates. The details have not been worked out yet, > but this is how is going to work. > > Best regards, > Andre Lorbach > > > > > > _______________________________________________ > phpLogCon mailing list > http://lists.adiscon.net/mailman/listinfo/phplogcon From alorbach at ro1.adiscon.com Thu May 15 15:04:57 2008 From: alorbach at ro1.adiscon.com (Andre Lorbach) Date: Thu, 15 May 2008 15:04:57 +0200 Subject: [phpLogCon] install.php remove or not In-Reply-To: <200805151457.25616.pvrabec@redhat.com> References: <200805141625.01176.pvrabec@redhat.com><200805151437.46121.pvrabec@redhat.com> <200805151457.25616.pvrabec@redhat.com> Message-ID: > -----Original Message----- > From: phplogcon-bounces at lists.adiscon.com [mailto:phplogcon- > bounces at lists.adiscon.com] On Behalf Of Peter Vrabec > Sent: Thursday, May 15, 2008 2:57 PM > To: phplogcon at lists.adiscon.com > Subject: Re: [phpLogCon] install.php remove or not > > ok. thnx. for answers Andre :) > > I'll do following: > * suggest users to rename config.php to something safe > * do not install install.php during package UPDATE > * restrict access to phplogcon, allowed only from localhost by default Sounds good to me :) Regarding the config.php, the default template is stored in the include directory called "config.sample.php". The config.php is created out of this template during the installation only. So you can savely copy all files over the old except for the install.php. Best regards, Andre Lorbach From pvrabec at redhat.com Fri May 16 15:22:14 2008 From: pvrabec at redhat.com (Peter Vrabec) Date: Fri, 16 May 2008 15:22:14 +0200 Subject: [phpLogCon] install.php remove or not In-Reply-To: References: <200805141625.01176.pvrabec@redhat.com> <200805151457.25616.pvrabec@redhat.com> Message-ID: <200805161522.15072.pvrabec@redhat.com> On Thursday 15 May 2008 03:04:57 pm Andre Lorbach wrote: > > -----Original Message----- > > From: phplogcon-bounces at lists.adiscon.com [mailto:phplogcon- > > bounces at lists.adiscon.com] On Behalf Of Peter Vrabec > > Sent: Thursday, May 15, 2008 2:57 PM > > To: phplogcon at lists.adiscon.com > > Subject: Re: [phpLogCon] install.php remove or not > > > > ok. thnx. for answers Andre :) > > > > I'll do following: > > * suggest users to rename config.php to something safe > > * do not install install.php during package UPDATE > > * restrict access to phplogcon, allowed only from localhost by default > > Sounds good to me :) > > Regarding the config.php, the default template is stored in the include > directory called "config.sample.php". The config.php is created out of > this template during the installation only. So you can savely copy all > files over the old except for the install.php. Ooops. Things around install.php are not going well. see: https://bugzilla.redhat.com/show_bug.cgi?id=444722 $ rpm -V phplogcon S.5....T c /etc/phplogcon/config.php missing /usr/share/phplogcon/install.php Do you think it would be possible to handle this problem different way? For example in install.php something like: if configured then { exit } else { do usual } > Best regards, > Andre Lorbach > _______________________________________________ > phpLogCon mailing list > http://lists.adiscon.net/mailman/listinfo/phplogcon From rgerhards at hq.adiscon.com Fri May 16 15:37:36 2008 From: rgerhards at hq.adiscon.com (Rainer Gerhards) Date: Fri, 16 May 2008 15:37:36 +0200 Subject: [phpLogCon] install.php remove or not In-Reply-To: <200805161522.15072.pvrabec@redhat.com> References: <200805141625.01176.pvrabec@redhat.com> <200805151457.25616.pvrabec@redhat.com> <200805161522.15072.pvrabec@redhat.com> Message-ID: <1210945056.22738.508.camel@localhost.localdomain> Hi Peter, I just talked with Andre. He told me that he is doing the same thing as e.g. phpBB. I think there is a RPM available for phpBB. Could you have a look at that RPM and tell us the difference? We could probably implement it along those lines... Rainer On Fri, 2008-05-16 at 15:22 +0200, Peter Vrabec wrote: > On Thursday 15 May 2008 03:04:57 pm Andre Lorbach wrote: > > > -----Original Message----- > > > From: phplogcon-bounces at lists.adiscon.com [mailto:phplogcon- > > > bounces at lists.adiscon.com] On Behalf Of Peter Vrabec > > > Sent: Thursday, May 15, 2008 2:57 PM > > > To: phplogcon at lists.adiscon.com > > > Subject: Re: [phpLogCon] install.php remove or not > > > > > > ok. thnx. for answers Andre :) > > > > > > I'll do following: > > > * suggest users to rename config.php to something safe > > > * do not install install.php during package UPDATE > > > * restrict access to phplogcon, allowed only from localhost by default > > > > Sounds good to me :) > > > > Regarding the config.php, the default template is stored in the include > > directory called "config.sample.php". The config.php is created out of > > this template during the installation only. So you can savely copy all > > files over the old except for the install.php. > > Ooops. Things around install.php are not going well. > see: https://bugzilla.redhat.com/show_bug.cgi?id=444722 > $ rpm -V phplogcon > S.5....T c /etc/phplogcon/config.php > missing /usr/share/phplogcon/install.php > > Do you think it would be possible to handle this problem different way? For > example in install.php something like: > if configured then { > exit > } > else { > do usual > } > > > > > > Best regards, > > Andre Lorbach > > _______________________________________________ > > phpLogCon mailing list > > http://lists.adiscon.net/mailman/listinfo/phplogcon > > > _______________________________________________ > phpLogCon mailing list > http://lists.adiscon.net/mailman/listinfo/phplogcon From alorbach at ro1.adiscon.com Fri May 16 15:53:22 2008 From: alorbach at ro1.adiscon.com (Andre Lorbach) Date: Fri, 16 May 2008 15:53:22 +0200 Subject: [phpLogCon] install.php remove or not In-Reply-To: <200805161522.15072.pvrabec@redhat.com> References: <200805141625.01176.pvrabec@redhat.com><200805151457.25616.pvrabec@redhat.com> <200805161522.15072.pvrabec@redhat.com> Message-ID: Hi, we could handle the configured / installed state different if we find no other way around this problem. But if possible I would like to find an alternative solution for the problem first. The installation method in phpLogCon is similar to the method used in phpbb. There is another thing that clearly tells you if phpLogCon was already configured, if the config.php file isn't empty anymore. By default an empty one with write access is shipped, right? This config.php file is written by the installation routine at the very end. So only if the config.php file is empty, the update needs to copy the install.php file. Is it possible to handle this by the package manager? -- Best regards, Andre Lorbach > -----Original Message----- > From: phplogcon-bounces at lists.adiscon.com [mailto:phplogcon- > bounces at lists.adiscon.com] On Behalf Of Peter Vrabec > Sent: Friday, May 16, 2008 3:22 PM > To: phplogcon at lists.adiscon.com > Subject: Re: [phpLogCon] install.php remove or not > > On Thursday 15 May 2008 03:04:57 pm Andre Lorbach wrote: > > > -----Original Message----- > > > From: phplogcon-bounces at lists.adiscon.com [mailto:phplogcon- > > > bounces at lists.adiscon.com] On Behalf Of Peter Vrabec > > > Sent: Thursday, May 15, 2008 2:57 PM > > > To: phplogcon at lists.adiscon.com > > > Subject: Re: [phpLogCon] install.php remove or not > > > > > > ok. thnx. for answers Andre :) > > > > > > I'll do following: > > > * suggest users to rename config.php to something safe > > > * do not install install.php during package UPDATE > > > * restrict access to phplogcon, allowed only from localhost by default > > > > Sounds good to me :) > > > > Regarding the config.php, the default template is stored in the include > > directory called "config.sample.php". The config.php is created out of > > this template during the installation only. So you can savely copy all > > files over the old except for the install.php. > > Ooops. Things around install.php are not going well. > see: https://bugzilla.redhat.com/show_bug.cgi?id=444722 > $ rpm -V phplogcon > S.5....T c /etc/phplogcon/config.php > missing /usr/share/phplogcon/install.php > > Do you think it would be possible to handle this problem different way? For > example in install.php something like: > if configured then { > exit > } > else { > do usual > } > > > > > > Best regards, > > Andre Lorbach > > _______________________________________________ > > phpLogCon mailing list > > http://lists.adiscon.net/mailman/listinfo/phplogcon > > > _______________________________________________ > phpLogCon mailing list > http://lists.adiscon.net/mailman/listinfo/phplogcon From rgerhards at hq.adiscon.com Fri May 16 15:55:45 2008 From: rgerhards at hq.adiscon.com (Rainer Gerhards) Date: Fri, 16 May 2008 15:55:45 +0200 Subject: [phpLogCon] install.php remove or not In-Reply-To: References: <200805141625.01176.pvrabec@redhat.com> <200805151457.25616.pvrabec@redhat.com> <200805161522.15072.pvrabec@redhat.com> Message-ID: <1210946145.22738.511.camel@localhost.localdomain> If I understood the bugzilla entry correctly, the empty file causes other grief ;) So it might be good to add a comment to it (e.g. /*NOTCONFIGURED*/\n). Then, you could check that comment. Two problems solved ;) Rainer On Fri, 2008-05-16 at 15:53 +0200, Andre Lorbach wrote: > Hi, > > we could handle the configured / installed state different if we find no > other way around this problem. But if possible I would like to find an > alternative solution for the problem first. > > The installation method in phpLogCon is similar to the method used in > phpbb. > > There is another thing that clearly tells you if phpLogCon was already > configured, if the config.php file isn't empty anymore. By default an > empty one with write access is shipped, right? This config.php file is > written by the installation routine at the very end. So only if the > config.php file is empty, the update needs to copy the install.php file. > Is it possible to handle this by the package manager? > > -- > Best regards, > Andre Lorbach > > > > > -----Original Message----- > > From: phplogcon-bounces at lists.adiscon.com [mailto:phplogcon- > > bounces at lists.adiscon.com] On Behalf Of Peter Vrabec > > Sent: Friday, May 16, 2008 3:22 PM > > To: phplogcon at lists.adiscon.com > > Subject: Re: [phpLogCon] install.php remove or not > > > > On Thursday 15 May 2008 03:04:57 pm Andre Lorbach wrote: > > > > -----Original Message----- > > > > From: phplogcon-bounces at lists.adiscon.com [mailto:phplogcon- > > > > bounces at lists.adiscon.com] On Behalf Of Peter Vrabec > > > > Sent: Thursday, May 15, 2008 2:57 PM > > > > To: phplogcon at lists.adiscon.com > > > > Subject: Re: [phpLogCon] install.php remove or not > > > > > > > > ok. thnx. for answers Andre :) > > > > > > > > I'll do following: > > > > * suggest users to rename config.php to something safe > > > > * do not install install.php during package UPDATE > > > > * restrict access to phplogcon, allowed only from localhost by > default > > > > > > Sounds good to me :) > > > > > > Regarding the config.php, the default template is stored in the > include > > > directory called "config.sample.php". The config.php is created out > of > > > this template during the installation only. So you can savely copy > all > > > files over the old except for the install.php. > > > > Ooops. Things around install.php are not going well. > > see: https://bugzilla.redhat.com/show_bug.cgi?id=444722 > > $ rpm -V phplogcon > > S.5....T c /etc/phplogcon/config.php > > missing /usr/share/phplogcon/install.php > > > > Do you think it would be possible to handle this problem different > way? For > > example in install.php something like: > > if configured then { > > exit > > } > > else { > > do usual > > } > > > > > > > > > > > Best regards, > > > Andre Lorbach > > > _______________________________________________ > > > phpLogCon mailing list > > > http://lists.adiscon.net/mailman/listinfo/phplogcon > > > > > > _______________________________________________ > > phpLogCon mailing list > > http://lists.adiscon.net/mailman/listinfo/phplogcon > _______________________________________________ > phpLogCon mailing list > http://lists.adiscon.net/mailman/listinfo/phplogcon From pvrabec at redhat.com Fri May 16 16:23:21 2008 From: pvrabec at redhat.com (Peter Vrabec) Date: Fri, 16 May 2008 16:23:21 +0200 Subject: [phpLogCon] install.php remove or not In-Reply-To: <1210946145.22738.511.camel@localhost.localdomain> References: <200805141625.01176.pvrabec@redhat.com> <1210946145.22738.511.camel@localhost.localdomain> Message-ID: <200805161623.21874.pvrabec@redhat.com> quick reply On Friday 16 May 2008 03:55:45 pm Rainer Gerhards wrote: > If I understood the bugzilla entry correctly, the empty file causes > other grief ;) > > So it might be good to add a comment to it (e.g. /*NOTCONFIGURED*/\n). > Then, you could check that comment. Two problems solved ;) I agree /*NOTCONFIGURED*/\n is good idea. > Rainer > > On Fri, 2008-05-16 at 15:53 +0200, Andre Lorbach wrote: > > Hi, > > > > we could handle the configured / installed state different if we find no > > other way around this problem. But if possible I would like to find an > > alternative solution for the problem first. > > > > The installation method in phpLogCon is similar to the method used in > > phpbb. Let me see. I can't find phpBB. :( > > There is another thing that clearly tells you if phpLogCon was already > > configured, if the config.php file isn't empty anymore. By default an > > empty one with write access is shipped, right? This config.php file is > > written by the installation routine at the very end. So only if the > > config.php file is empty, the update needs to copy the install.php file. > > Is it possible to handle this by the package manager? I'm afraid it's not possible. I can only remove the file if it was an update. But then there is rpm -V problem. From alorbach at ro1.adiscon.com Fri May 16 16:44:59 2008 From: alorbach at ro1.adiscon.com (Andre Lorbach) Date: Fri, 16 May 2008 16:44:59 +0200 Subject: [phpLogCon] install.php remove or not In-Reply-To: <200805161623.21874.pvrabec@redhat.com> References: <200805141625.01176.pvrabec@redhat.com><1210946145.22738.511.camel@localhost.localdomain> <200805161623.21874.pvrabec@redhat.com> Message-ID: > On Friday 16 May 2008 03:55:45 pm Rainer Gerhards wrote: > > If I understood the bugzilla entry correctly, the empty file causes > > other grief ;) > > > > So it might be good to add a comment to it (e.g. /*NOTCONFIGURED*/\n). > > Then, you could check that comment. Two problems solved ;) > I agree /*NOTCONFIGURED*/\n is good idea. > > > Rainer > > > > On Fri, 2008-05-16 at 15:53 +0200, Andre Lorbach wrote: > > > Hi, > > > > > > we could handle the configured / installed state different if we find no > > > other way around this problem. But if possible I would like to find an > > > alternative solution for the problem first. > > > > > > The installation method in phpLogCon is similar to the method used in > > > phpbb. > Let me see. I can't find phpBB. :( > > > > There is another thing that clearly tells you if phpLogCon was already > > > configured, if the config.php file isn't empty anymore. By default an > > > empty one with write access is shipped, right? This config.php file is > > > written by the installation routine at the very end. So only if the > > > config.php file is empty, the update needs to copy the install.php file. > > > Is it possible to handle this by the package manager? > I'm afraid it's not possible. I can only remove the file if it was an update. > But then there is rpm -V problem. Ok what I can do is, I can add a check like I described above. If the config.php is empty, this means install.php is allowed to run. If the size of config.php is more then 0, the install.php script will deny any attempt to open it. In order to reconfigure phpLogCon, the config.php file would need to be deleted or replaced with an empty one. -- Best regards, Andre Lorbach From pvrabec at redhat.com Fri May 16 16:55:25 2008 From: pvrabec at redhat.com (Peter Vrabec) Date: Fri, 16 May 2008 16:55:25 +0200 Subject: [phpLogCon] install.php remove or not In-Reply-To: References: <200805141625.01176.pvrabec@redhat.com> <200805161623.21874.pvrabec@redhat.com> Message-ID: <200805161655.25421.pvrabec@redhat.com> On Friday 16 May 2008 04:44:59 pm Andre Lorbach wrote: > > On Friday 16 May 2008 03:55:45 pm Rainer Gerhards wrote: > > > If I understood the bugzilla entry correctly, the empty file causes > > > other grief ;) > > > > > > So it might be good to add a comment to it (e.g. > > /*NOTCONFIGURED*/\n). > > > > Then, you could check that comment. Two problems solved ;) > > > > I agree /*NOTCONFIGURED*/\n is good idea. > > > > > Rainer > > > > > > On Fri, 2008-05-16 at 15:53 +0200, Andre Lorbach wrote: > > > > Hi, > > > > > > > > we could handle the configured / installed state different if we > > find no > > > > > other way around this problem. But if possible I would like to > > find an > > > > > alternative solution for the problem first. > > > > > > > > The installation method in phpLogCon is similar to the method used > > in > > > > > phpbb. > > > > Let me see. I can't find phpBB. :( > > > > > > There is another thing that clearly tells you if phpLogCon was > > already > > > > > configured, if the config.php file isn't empty anymore. By default > > an > > > > > empty one with write access is shipped, right? This config.php > > file is > > > > > written by the installation routine at the very end. So only if > > the > > > > > config.php file is empty, the update needs to copy the install.php > > file. > > > > > Is it possible to handle this by the package manager? > > > > I'm afraid it's not possible. I can only remove the file if it was an > > update. > > > But then there is rpm -V problem. > > Ok what I can do is, I can add a check like I described above. If the > config.php is empty, this means install.php is allowed to run. If the > size of config.php is more then 0, the install.php script will deny any > attempt to open it. In order to reconfigure phpLogCon, the config.php > file would need to be deleted or replaced with an empty one. thnx. Andre, I think this will push us further. I'm sorry I thought I can handle it in spec file, but I was wrong. I hope it helps other distros too. > Best regards, > Andre Lorbach > _______________________________________________ > phpLogCon mailing list > http://lists.adiscon.net/mailman/listinfo/phplogcon From alorbach at ro1.adiscon.com Fri May 16 16:57:10 2008 From: alorbach at ro1.adiscon.com (Andre Lorbach) Date: Fri, 16 May 2008 16:57:10 +0200 Subject: [phpLogCon] install.php remove or not In-Reply-To: <200805161655.25421.pvrabec@redhat.com> References: <200805141625.01176.pvrabec@redhat.com><200805161623.21874.pvrabec@redhat.com> <200805161655.25421.pvrabec@redhat.com> Message-ID: > I'm afraid it's not possible. I can only remove the file if it was an > > > > update. > > > > > But then there is rpm -V problem. > > > > Ok what I can do is, I can add a check like I described above. If the > > config.php is empty, this means install.php is allowed to run. If the > > size of config.php is more then 0, the install.php script will deny any > > attempt to open it. In order to reconfigure phpLogCon, the config.php > > file would need to be deleted or replaced with an empty one. > > thnx. Andre, I think this will push us further. I'm sorry I thought I can > handle it in spec file, but I was wrong. I hope it helps other distros too. No problem ;) - the more I think about this, the more I like this way to handle the install.php. -- Best regards, Andre Lorbach From alorbach at ro1.adiscon.com Mon May 19 15:40:07 2008 From: alorbach at ro1.adiscon.com (Andre Lorbach) Date: Mon, 19 May 2008 15:40:07 +0200 Subject: [phpLogCon] install.php remove or not In-Reply-To: <200805161655.25421.pvrabec@redhat.com> References: <200805141625.01176.pvrabec@redhat.com><200805161623.21874.pvrabec@redhat.com> <200805161655.25421.pvrabec@redhat.com> Message-ID: Hi again ;)! I want to inform you that I have made the changes in the current beta branch today. >From the changelog: Changed install.php handling, so it is not necessary to remove the script anymore. To avoid problems with automatic package updating, we changed the installer handling. From now, the install.php will be allowed to run only in two cases, first if the config.php file is missing, and second if the config.php file is empty. Download available from here: http://www.phplogcon.org/downloads The devel branch will be updated tomorrow. -- Best regards, Andre Lorbach > > update. > > > > > But then there is rpm -V problem. > > > > Ok what I can do is, I can add a check like I described above. If the > > config.php is empty, this means install.php is allowed to run. If the > > size of config.php is more then 0, the install.php script will deny any > > attempt to open it. In order to reconfigure phpLogCon, the config.php > > file would need to be deleted or replaced with an empty one. > > thnx. Andre, I think this will push us further. I'm sorry I thought I can > handle it in spec file, but I was wrong. I hope it helps other distros too. From alorbach at ro1.adiscon.com Tue May 20 16:59:17 2008 From: alorbach at ro1.adiscon.com (Andre Lorbach) Date: Tue, 20 May 2008 16:59:17 +0200 Subject: [phpLogCon] install.php remove or not In-Reply-To: References: <200805141625.01176.pvrabec@redhat.com><200805161623.21874.pvrabec@redhat.com><200805161655.25421.pvrabec@redhat.com> Message-ID: Hi again #2 ^^, as promised yesterday, here is the new Version from the devel branch v2.3.2, available from here: http://www.phplogcon.org/Downloads-req-viewdownloaddetails-lid-15.phtml The new version contains the install handling change from yesterday. Best regards, Andre Lorbach > -----Original Message----- > From: phplogcon-bounces at lists.adiscon.com [mailto:phplogcon- > bounces at lists.adiscon.com] On Behalf Of Andre Lorbach > Sent: Monday, May 19, 2008 3:40 PM > To: phplogcon at lists.adiscon.com > Subject: Re: [phpLogCon] install.php remove or not > > Hi again ;)! > > I want to inform you that I have made the changes in the current beta > branch today. > >From the changelog: > > Changed install.php handling, so it is not necessary to remove > the script anymore. > > To avoid problems with automatic package updating, we changed > the installer handling. > From now, the install.php will be allowed to run only in two > cases, first if the > config.php file is missing, and second if the config.php file is > empty. > > Download available from here: > http://www.phplogcon.org/downloads > > The devel branch will be updated tomorrow. > > -- > Best regards, > Andre Lorbach > > > > update. > > > > > > > But then there is rpm -V problem. > > > > > > Ok what I can do is, I can add a check like I described above. If > the > > > config.php is empty, this means install.php is allowed to run. If > the > > > size of config.php is more then 0, the install.php script will deny > any > > > attempt to open it. In order to reconfigure phpLogCon, the > config.php > > > file would need to be deleted or replaced with an empty one. > > > > thnx. Andre, I think this will push us further. I'm sorry I thought I > can > > handle it in spec file, but I was wrong. I hope it helps other distros > too. > > _______________________________________________ > phpLogCon mailing list > http://lists.adiscon.net/mailman/listinfo/phplogcon From pvrabec at redhat.com Tue May 27 10:58:44 2008 From: pvrabec at redhat.com (Peter Vrabec) Date: Tue, 27 May 2008 10:58:44 +0200 Subject: [phpLogCon] good news everyone :) Message-ID: <200805271058.44324.pvrabec@redhat.com> phplogcon passed the review finally. It was built in F9 and rawhide(F10), so I hope it will be available in fedora repositories soon. From alorbach at ro1.adiscon.com Tue May 27 11:01:19 2008 From: alorbach at ro1.adiscon.com (Andre Lorbach) Date: Tue, 27 May 2008 11:01:19 +0200 Subject: [phpLogCon] good news everyone :) In-Reply-To: <200805271058.44324.pvrabec@redhat.com> References: <200805271058.44324.pvrabec@redhat.com> Message-ID: Awesome news :) Great to hear that . Best regards, Andre Lorbach > -----Original Message----- > From: phplogcon-bounces at lists.adiscon.com [mailto:phplogcon- > bounces at lists.adiscon.com] On Behalf Of Peter Vrabec > Sent: Tuesday, May 27, 2008 10:59 AM > To: phplogcon at lists.adiscon.com > Subject: [phpLogCon] good news everyone :) > > phplogcon passed the review finally. It was built in F9 and rawhide(F10), so I > hope it will be available in fedora repositories soon. > _______________________________________________ > phpLogCon mailing list > http://lists.adiscon.net/mailman/listinfo/phplogcon From pvrabec at redhat.com Fri May 2 11:31:13 2008 From: pvrabec at redhat.com (Peter Vrabec) Date: Fri, 2 May 2008 11:31:13 +0200 Subject: [phpLogCon] phplogcon-2.1.3 Message-ID: <200805021131.13085.pvrabec@redhat.com> Hi folks, thnx. for phplogcon, v2.1.3 works fine. I have submitted review request for inclusion in Fedora. https://bugzilla.redhat.com/show_bug.cgi?id=444722. From pvrabec at redhat.com Fri May 2 11:17:15 2008 From: pvrabec at redhat.com (Peter Vrabec) Date: Fri, 2 May 2008 11:17:15 +0200 Subject: [phpLogCon] phplogcon-2.1.3 Message-ID: <200805021117.15997.pvrabec@redhat.com> Hi folks, thnx. for phplogcon, v2.1.3 works fine. I have submitted review request for inclusion in Fedora. https://bugzilla.redhat.com/show_bug.cgi?id=444722. From friedl at hq.adiscon.com Fri May 2 16:19:46 2008 From: friedl at hq.adiscon.com (Florian Riedl) Date: Fri, 2 May 2008 16:19:46 +0200 Subject: [phpLogCon] phpLogCon 2.3.0 released Message-ID: <577465F99B41C842AAFBE9ED71E70ABA308F37@grfint2.intern.adiscon.com> Hi all, we have released phpLogCon 2.3.0, the first release of a new feature-enriched development branch. Version's 2.1.x are now on the beta branch and set to stabilize over the next few weeks (in short, this means they will receive bug fixes, but no new features). Version 2.3.0 provides changed database drivers with much better performance, especially for large databases. It also features new context-sensitive popup menus, which enable to quickly filter on some items. These menus are an important new technology that will be utilized in the future for enhanced troubleshooting capabilities. Download: http://www.phplogcon.org/Downloads-req-viewdownloaddetails-lid-11.phtml Florian Riedl From rgerhards at hq.adiscon.com Sat May 3 11:11:15 2008 From: rgerhards at hq.adiscon.com (Rainer Gerhards) Date: Sat, 3 May 2008 11:11:15 +0200 Subject: [phpLogCon] phpLogCon 2.3.1 released Message-ID: <577465F99B41C842AAFBE9ED71E70ABA308F3C@grfint2.intern.adiscon.com> Hi all, we have released version 2.3.1 of phpLogCon. This version provides an auto-reload functionality (automatic tail of logfiles), adds support for http gzip compression and improved the page title. This is a recommended update for all development branch users. Details and Download: http://www.phplogcon.org/downloads We hoipe this release is useful. As always, feedback is appreciated. Rainer From pvrabec at redhat.com Wed May 14 16:25:01 2008 From: pvrabec at redhat.com (Peter Vrabec) Date: Wed, 14 May 2008 16:25:01 +0200 Subject: [phpLogCon] install.php remove or not Message-ID: <200805141625.01176.pvrabec@redhat.com> Hi folks, I have a Q. for you. It's suggested that install.php should be removed after configuration. Is this behavior OK? What if someone want to do another configuration? When you done the configuration, removed install.php and do the package update. Should or shouldn't be install.php installed? I thing it shouldn't, but we need to handle this problem inside rpm. From alorbach at ro1.adiscon.com Thu May 15 10:31:52 2008 From: alorbach at ro1.adiscon.com (Andre Lorbach) Date: Thu, 15 May 2008 10:31:52 +0200 Subject: [phpLogCon] install.php remove or not In-Reply-To: <200805141625.01176.pvrabec@redhat.com> References: <200805141625.01176.pvrabec@redhat.com> Message-ID: Hi, these are good questions ;). The behavior is wanted, the install.php script needs to be removed/renamed after installation, otherwise it would be possible to overwrite the users config.php by running the installation again. The user will be able to set options within phpLogCon at some point in future versions. When the package is updated, install.php should not be installed. If there is an update needed in future, phpLogCon will handle it with an update script. -- I hope this helps - best regards, Andre Lorbach > -----Original Message----- > From: phplogcon-bounces at lists.adiscon.com [mailto:phplogcon- > bounces at lists.adiscon.com] On Behalf Of Peter Vrabec > Sent: Wednesday, May 14, 2008 4:25 PM > To: phplogcon at lists.adiscon.com > Subject: [phpLogCon] install.php remove or not > > Hi folks, > > I have a Q. for you. > > It's suggested that install.php should be removed after configuration. Is this > behavior OK? What if someone want to do another configuration? > > When you done the configuration, removed install.php and do the package > update. Should or shouldn't be install.php installed? I thing it shouldn't, > but we need to handle this problem inside rpm. > _______________________________________________ > phpLogCon mailing list > http://lists.adiscon.net/mailman/listinfo/phplogcon From pvrabec at redhat.com Thu May 15 14:37:46 2008 From: pvrabec at redhat.com (Peter Vrabec) Date: Thu, 15 May 2008 14:37:46 +0200 Subject: [phpLogCon] install.php remove or not In-Reply-To: References: <200805141625.01176.pvrabec@redhat.com> Message-ID: <200805151437.46121.pvrabec@redhat.com> Hi, On Thursday 15 May 2008 10:31:52 am Andre Lorbach wrote: > Hi, > > these are good questions ;). > > The behavior is wanted, the install.php script needs to be > removed/renamed after installation, otherwise it would be possible to > overwrite the users config.php by running the installation again. I think we can control access via apache configuration. install.php allowed only from localhost. > The > user will be able to set options within phpLogCon at some point in > future versions. What do you mean "set options"? Edit config file? > When the package is updated, install.php should not be installed. This won't be problem. > If > there is an update needed in future, phpLogCon will handle it with an > update script. Could you explain it little more. > -- > I hope this helps - best regards, > Andre Lorbach > > > -----Original Message----- > > From: phplogcon-bounces at lists.adiscon.com [mailto:phplogcon- > > bounces at lists.adiscon.com] On Behalf Of Peter Vrabec > > Sent: Wednesday, May 14, 2008 4:25 PM > > To: phplogcon at lists.adiscon.com > > Subject: [phpLogCon] install.php remove or not > > > > Hi folks, > > > > I have a Q. for you. > > > > It's suggested that install.php should be removed after configuration. > > Is this > > > behavior OK? What if someone want to do another configuration? > > > > When you done the configuration, removed install.php and do the > > package > > > update. Should or shouldn't be install.php installed? I thing it > > shouldn't, > > > but we need to handle this problem inside rpm. > > _______________________________________________ > > phpLogCon mailing list > > http://lists.adiscon.net/mailman/listinfo/phplogcon > > _______________________________________________ > phpLogCon mailing list > http://lists.adiscon.net/mailman/listinfo/phplogcon From alorbach at ro1.adiscon.com Thu May 15 14:48:49 2008 From: alorbach at ro1.adiscon.com (Andre Lorbach) Date: Thu, 15 May 2008 14:48:49 +0200 Subject: [phpLogCon] install.php remove or not In-Reply-To: <200805151437.46121.pvrabec@redhat.com> References: <200805141625.01176.pvrabec@redhat.com> <200805151437.46121.pvrabec@redhat.com> Message-ID: > -----Original Message----- > From: phplogcon-bounces at lists.adiscon.com [mailto:phplogcon- > bounces at lists.adiscon.com] On Behalf Of Peter Vrabec > Sent: Thursday, May 15, 2008 2:38 PM > To: phplogcon at lists.adiscon.com > Subject: Re: [phpLogCon] install.php remove or not > > Hi, > > On Thursday 15 May 2008 10:31:52 am Andre Lorbach wrote: > > Hi, > > > > these are good questions ;). > > > > The behavior is wanted, the install.php script needs to be > > removed/renamed after installation, otherwise it would be possible to > > overwrite the users config.php by running the installation again. > I think we can control access via apache configuration. install.php allowed > only from localhost. > > > The > > user will be able to set options within phpLogCon at some point in > > future versions. > What do you mean "set options"? Edit config file? Yes once we have a user management system implemented, which can be turned on and off optionally, the user will be able to configure all the options within phpLogCon user interface. > > When the package is updated, install.php should not be installed. > This won't be problem. > > > If > > there is an update needed in future, phpLogCon will handle it with an > > update script. > Could you explain it little more. There will be some kind of update.php which can only be access by authorized users (requires the user management system) which will detect and perform necessary updates. The details have not been worked out yet, but this is how is going to work. Best regards, Andre Lorbach From pvrabec at redhat.com Thu May 15 14:57:25 2008 From: pvrabec at redhat.com (Peter Vrabec) Date: Thu, 15 May 2008 14:57:25 +0200 Subject: [phpLogCon] install.php remove or not In-Reply-To: References: <200805141625.01176.pvrabec@redhat.com> <200805151437.46121.pvrabec@redhat.com> Message-ID: <200805151457.25616.pvrabec@redhat.com> ok. thnx. for answers Andre :) I'll do following: * suggest users to rename config.php to something safe * do not install install.php during package UPDATE * restrict access to phplogcon, allowed only from localhost by default On Thursday 15 May 2008 02:48:49 pm Andre Lorbach wrote: > > -----Original Message----- > > From: phplogcon-bounces at lists.adiscon.com [mailto:phplogcon- > > bounces at lists.adiscon.com] On Behalf Of Peter Vrabec > > Sent: Thursday, May 15, 2008 2:38 PM > > To: phplogcon at lists.adiscon.com > > Subject: Re: [phpLogCon] install.php remove or not > > > > Hi, > > > > On Thursday 15 May 2008 10:31:52 am Andre Lorbach wrote: > > > Hi, > > > > > > these are good questions ;). > > > > > > The behavior is wanted, the install.php script needs to be > > > removed/renamed after installation, otherwise it would be possible > > to > > > > overwrite the users config.php by running the installation again. > > > > I think we can control access via apache configuration. install.php > > allowed > > > only from localhost. > > > > > The > > > user will be able to set options within phpLogCon at some point in > > > future versions. > > > > What do you mean "set options"? Edit config file? > > Yes once we have a user management system implemented, which can be > turned on and off optionally, the user will be able to configure all the > options within phpLogCon user interface. > > > > When the package is updated, install.php should not be installed. > > > > This won't be problem. > > > > > If > > > there is an update needed in future, phpLogCon will handle it with > > an > > > > update script. > > > > Could you explain it little more. > > There will be some kind of update.php which can only be access by > authorized users (requires the user management system) which will detect > and perform necessary updates. The details have not been worked out yet, > but this is how is going to work. > > Best regards, > Andre Lorbach > > > > > > _______________________________________________ > phpLogCon mailing list > http://lists.adiscon.net/mailman/listinfo/phplogcon From alorbach at ro1.adiscon.com Thu May 15 15:04:57 2008 From: alorbach at ro1.adiscon.com (Andre Lorbach) Date: Thu, 15 May 2008 15:04:57 +0200 Subject: [phpLogCon] install.php remove or not In-Reply-To: <200805151457.25616.pvrabec@redhat.com> References: <200805141625.01176.pvrabec@redhat.com><200805151437.46121.pvrabec@redhat.com> <200805151457.25616.pvrabec@redhat.com> Message-ID: > -----Original Message----- > From: phplogcon-bounces at lists.adiscon.com [mailto:phplogcon- > bounces at lists.adiscon.com] On Behalf Of Peter Vrabec > Sent: Thursday, May 15, 2008 2:57 PM > To: phplogcon at lists.adiscon.com > Subject: Re: [phpLogCon] install.php remove or not > > ok. thnx. for answers Andre :) > > I'll do following: > * suggest users to rename config.php to something safe > * do not install install.php during package UPDATE > * restrict access to phplogcon, allowed only from localhost by default Sounds good to me :) Regarding the config.php, the default template is stored in the include directory called "config.sample.php". The config.php is created out of this template during the installation only. So you can savely copy all files over the old except for the install.php. Best regards, Andre Lorbach From pvrabec at redhat.com Fri May 16 15:22:14 2008 From: pvrabec at redhat.com (Peter Vrabec) Date: Fri, 16 May 2008 15:22:14 +0200 Subject: [phpLogCon] install.php remove or not In-Reply-To: References: <200805141625.01176.pvrabec@redhat.com> <200805151457.25616.pvrabec@redhat.com> Message-ID: <200805161522.15072.pvrabec@redhat.com> On Thursday 15 May 2008 03:04:57 pm Andre Lorbach wrote: > > -----Original Message----- > > From: phplogcon-bounces at lists.adiscon.com [mailto:phplogcon- > > bounces at lists.adiscon.com] On Behalf Of Peter Vrabec > > Sent: Thursday, May 15, 2008 2:57 PM > > To: phplogcon at lists.adiscon.com > > Subject: Re: [phpLogCon] install.php remove or not > > > > ok. thnx. for answers Andre :) > > > > I'll do following: > > * suggest users to rename config.php to something safe > > * do not install install.php during package UPDATE > > * restrict access to phplogcon, allowed only from localhost by default > > Sounds good to me :) > > Regarding the config.php, the default template is stored in the include > directory called "config.sample.php". The config.php is created out of > this template during the installation only. So you can savely copy all > files over the old except for the install.php. Ooops. Things around install.php are not going well. see: https://bugzilla.redhat.com/show_bug.cgi?id=444722 $ rpm -V phplogcon S.5....T c /etc/phplogcon/config.php missing /usr/share/phplogcon/install.php Do you think it would be possible to handle this problem different way? For example in install.php something like: if configured then { exit } else { do usual } > Best regards, > Andre Lorbach > _______________________________________________ > phpLogCon mailing list > http://lists.adiscon.net/mailman/listinfo/phplogcon From rgerhards at hq.adiscon.com Fri May 16 15:37:36 2008 From: rgerhards at hq.adiscon.com (Rainer Gerhards) Date: Fri, 16 May 2008 15:37:36 +0200 Subject: [phpLogCon] install.php remove or not In-Reply-To: <200805161522.15072.pvrabec@redhat.com> References: <200805141625.01176.pvrabec@redhat.com> <200805151457.25616.pvrabec@redhat.com> <200805161522.15072.pvrabec@redhat.com> Message-ID: <1210945056.22738.508.camel@localhost.localdomain> Hi Peter, I just talked with Andre. He told me that he is doing the same thing as e.g. phpBB. I think there is a RPM available for phpBB. Could you have a look at that RPM and tell us the difference? We could probably implement it along those lines... Rainer On Fri, 2008-05-16 at 15:22 +0200, Peter Vrabec wrote: > On Thursday 15 May 2008 03:04:57 pm Andre Lorbach wrote: > > > -----Original Message----- > > > From: phplogcon-bounces at lists.adiscon.com [mailto:phplogcon- > > > bounces at lists.adiscon.com] On Behalf Of Peter Vrabec > > > Sent: Thursday, May 15, 2008 2:57 PM > > > To: phplogcon at lists.adiscon.com > > > Subject: Re: [phpLogCon] install.php remove or not > > > > > > ok. thnx. for answers Andre :) > > > > > > I'll do following: > > > * suggest users to rename config.php to something safe > > > * do not install install.php during package UPDATE > > > * restrict access to phplogcon, allowed only from localhost by default > > > > Sounds good to me :) > > > > Regarding the config.php, the default template is stored in the include > > directory called "config.sample.php". The config.php is created out of > > this template during the installation only. So you can savely copy all > > files over the old except for the install.php. > > Ooops. Things around install.php are not going well. > see: https://bugzilla.redhat.com/show_bug.cgi?id=444722 > $ rpm -V phplogcon > S.5....T c /etc/phplogcon/config.php > missing /usr/share/phplogcon/install.php > > Do you think it would be possible to handle this problem different way? For > example in install.php something like: > if configured then { > exit > } > else { > do usual > } > > > > > > Best regards, > > Andre Lorbach > > _______________________________________________ > > phpLogCon mailing list > > http://lists.adiscon.net/mailman/listinfo/phplogcon > > > _______________________________________________ > phpLogCon mailing list > http://lists.adiscon.net/mailman/listinfo/phplogcon From alorbach at ro1.adiscon.com Fri May 16 15:53:22 2008 From: alorbach at ro1.adiscon.com (Andre Lorbach) Date: Fri, 16 May 2008 15:53:22 +0200 Subject: [phpLogCon] install.php remove or not In-Reply-To: <200805161522.15072.pvrabec@redhat.com> References: <200805141625.01176.pvrabec@redhat.com><200805151457.25616.pvrabec@redhat.com> <200805161522.15072.pvrabec@redhat.com> Message-ID: Hi, we could handle the configured / installed state different if we find no other way around this problem. But if possible I would like to find an alternative solution for the problem first. The installation method in phpLogCon is similar to the method used in phpbb. There is another thing that clearly tells you if phpLogCon was already configured, if the config.php file isn't empty anymore. By default an empty one with write access is shipped, right? This config.php file is written by the installation routine at the very end. So only if the config.php file is empty, the update needs to copy the install.php file. Is it possible to handle this by the package manager? -- Best regards, Andre Lorbach > -----Original Message----- > From: phplogcon-bounces at lists.adiscon.com [mailto:phplogcon- > bounces at lists.adiscon.com] On Behalf Of Peter Vrabec > Sent: Friday, May 16, 2008 3:22 PM > To: phplogcon at lists.adiscon.com > Subject: Re: [phpLogCon] install.php remove or not > > On Thursday 15 May 2008 03:04:57 pm Andre Lorbach wrote: > > > -----Original Message----- > > > From: phplogcon-bounces at lists.adiscon.com [mailto:phplogcon- > > > bounces at lists.adiscon.com] On Behalf Of Peter Vrabec > > > Sent: Thursday, May 15, 2008 2:57 PM > > > To: phplogcon at lists.adiscon.com > > > Subject: Re: [phpLogCon] install.php remove or not > > > > > > ok. thnx. for answers Andre :) > > > > > > I'll do following: > > > * suggest users to rename config.php to something safe > > > * do not install install.php during package UPDATE > > > * restrict access to phplogcon, allowed only from localhost by default > > > > Sounds good to me :) > > > > Regarding the config.php, the default template is stored in the include > > directory called "config.sample.php". The config.php is created out of > > this template during the installation only. So you can savely copy all > > files over the old except for the install.php. > > Ooops. Things around install.php are not going well. > see: https://bugzilla.redhat.com/show_bug.cgi?id=444722 > $ rpm -V phplogcon > S.5....T c /etc/phplogcon/config.php > missing /usr/share/phplogcon/install.php > > Do you think it would be possible to handle this problem different way? For > example in install.php something like: > if configured then { > exit > } > else { > do usual > } > > > > > > Best regards, > > Andre Lorbach > > _______________________________________________ > > phpLogCon mailing list > > http://lists.adiscon.net/mailman/listinfo/phplogcon > > > _______________________________________________ > phpLogCon mailing list > http://lists.adiscon.net/mailman/listinfo/phplogcon From rgerhards at hq.adiscon.com Fri May 16 15:55:45 2008 From: rgerhards at hq.adiscon.com (Rainer Gerhards) Date: Fri, 16 May 2008 15:55:45 +0200 Subject: [phpLogCon] install.php remove or not In-Reply-To: References: <200805141625.01176.pvrabec@redhat.com> <200805151457.25616.pvrabec@redhat.com> <200805161522.15072.pvrabec@redhat.com> Message-ID: <1210946145.22738.511.camel@localhost.localdomain> If I understood the bugzilla entry correctly, the empty file causes other grief ;) So it might be good to add a comment to it (e.g. /*NOTCONFIGURED*/\n). Then, you could check that comment. Two problems solved ;) Rainer On Fri, 2008-05-16 at 15:53 +0200, Andre Lorbach wrote: > Hi, > > we could handle the configured / installed state different if we find no > other way around this problem. But if possible I would like to find an > alternative solution for the problem first. > > The installation method in phpLogCon is similar to the method used in > phpbb. > > There is another thing that clearly tells you if phpLogCon was already > configured, if the config.php file isn't empty anymore. By default an > empty one with write access is shipped, right? This config.php file is > written by the installation routine at the very end. So only if the > config.php file is empty, the update needs to copy the install.php file. > Is it possible to handle this by the package manager? > > -- > Best regards, > Andre Lorbach > > > > > -----Original Message----- > > From: phplogcon-bounces at lists.adiscon.com [mailto:phplogcon- > > bounces at lists.adiscon.com] On Behalf Of Peter Vrabec > > Sent: Friday, May 16, 2008 3:22 PM > > To: phplogcon at lists.adiscon.com > > Subject: Re: [phpLogCon] install.php remove or not > > > > On Thursday 15 May 2008 03:04:57 pm Andre Lorbach wrote: > > > > -----Original Message----- > > > > From: phplogcon-bounces at lists.adiscon.com [mailto:phplogcon- > > > > bounces at lists.adiscon.com] On Behalf Of Peter Vrabec > > > > Sent: Thursday, May 15, 2008 2:57 PM > > > > To: phplogcon at lists.adiscon.com > > > > Subject: Re: [phpLogCon] install.php remove or not > > > > > > > > ok. thnx. for answers Andre :) > > > > > > > > I'll do following: > > > > * suggest users to rename config.php to something safe > > > > * do not install install.php during package UPDATE > > > > * restrict access to phplogcon, allowed only from localhost by > default > > > > > > Sounds good to me :) > > > > > > Regarding the config.php, the default template is stored in the > include > > > directory called "config.sample.php". The config.php is created out > of > > > this template during the installation only. So you can savely copy > all > > > files over the old except for the install.php. > > > > Ooops. Things around install.php are not going well. > > see: https://bugzilla.redhat.com/show_bug.cgi?id=444722 > > $ rpm -V phplogcon > > S.5....T c /etc/phplogcon/config.php > > missing /usr/share/phplogcon/install.php > > > > Do you think it would be possible to handle this problem different > way? For > > example in install.php something like: > > if configured then { > > exit > > } > > else { > > do usual > > } > > > > > > > > > > > Best regards, > > > Andre Lorbach > > > _______________________________________________ > > > phpLogCon mailing list > > > http://lists.adiscon.net/mailman/listinfo/phplogcon > > > > > > _______________________________________________ > > phpLogCon mailing list > > http://lists.adiscon.net/mailman/listinfo/phplogcon > _______________________________________________ > phpLogCon mailing list > http://lists.adiscon.net/mailman/listinfo/phplogcon From pvrabec at redhat.com Fri May 16 16:23:21 2008 From: pvrabec at redhat.com (Peter Vrabec) Date: Fri, 16 May 2008 16:23:21 +0200 Subject: [phpLogCon] install.php remove or not In-Reply-To: <1210946145.22738.511.camel@localhost.localdomain> References: <200805141625.01176.pvrabec@redhat.com> <1210946145.22738.511.camel@localhost.localdomain> Message-ID: <200805161623.21874.pvrabec@redhat.com> quick reply On Friday 16 May 2008 03:55:45 pm Rainer Gerhards wrote: > If I understood the bugzilla entry correctly, the empty file causes > other grief ;) > > So it might be good to add a comment to it (e.g. /*NOTCONFIGURED*/\n). > Then, you could check that comment. Two problems solved ;) I agree /*NOTCONFIGURED*/\n is good idea. > Rainer > > On Fri, 2008-05-16 at 15:53 +0200, Andre Lorbach wrote: > > Hi, > > > > we could handle the configured / installed state different if we find no > > other way around this problem. But if possible I would like to find an > > alternative solution for the problem first. > > > > The installation method in phpLogCon is similar to the method used in > > phpbb. Let me see. I can't find phpBB. :( > > There is another thing that clearly tells you if phpLogCon was already > > configured, if the config.php file isn't empty anymore. By default an > > empty one with write access is shipped, right? This config.php file is > > written by the installation routine at the very end. So only if the > > config.php file is empty, the update needs to copy the install.php file. > > Is it possible to handle this by the package manager? I'm afraid it's not possible. I can only remove the file if it was an update. But then there is rpm -V problem. From alorbach at ro1.adiscon.com Fri May 16 16:44:59 2008 From: alorbach at ro1.adiscon.com (Andre Lorbach) Date: Fri, 16 May 2008 16:44:59 +0200 Subject: [phpLogCon] install.php remove or not In-Reply-To: <200805161623.21874.pvrabec@redhat.com> References: <200805141625.01176.pvrabec@redhat.com><1210946145.22738.511.camel@localhost.localdomain> <200805161623.21874.pvrabec@redhat.com> Message-ID: > On Friday 16 May 2008 03:55:45 pm Rainer Gerhards wrote: > > If I understood the bugzilla entry correctly, the empty file causes > > other grief ;) > > > > So it might be good to add a comment to it (e.g. /*NOTCONFIGURED*/\n). > > Then, you could check that comment. Two problems solved ;) > I agree /*NOTCONFIGURED*/\n is good idea. > > > Rainer > > > > On Fri, 2008-05-16 at 15:53 +0200, Andre Lorbach wrote: > > > Hi, > > > > > > we could handle the configured / installed state different if we find no > > > other way around this problem. But if possible I would like to find an > > > alternative solution for the problem first. > > > > > > The installation method in phpLogCon is similar to the method used in > > > phpbb. > Let me see. I can't find phpBB. :( > > > > There is another thing that clearly tells you if phpLogCon was already > > > configured, if the config.php file isn't empty anymore. By default an > > > empty one with write access is shipped, right? This config.php file is > > > written by the installation routine at the very end. So only if the > > > config.php file is empty, the update needs to copy the install.php file. > > > Is it possible to handle this by the package manager? > I'm afraid it's not possible. I can only remove the file if it was an update. > But then there is rpm -V problem. Ok what I can do is, I can add a check like I described above. If the config.php is empty, this means install.php is allowed to run. If the size of config.php is more then 0, the install.php script will deny any attempt to open it. In order to reconfigure phpLogCon, the config.php file would need to be deleted or replaced with an empty one. -- Best regards, Andre Lorbach From pvrabec at redhat.com Fri May 16 16:55:25 2008 From: pvrabec at redhat.com (Peter Vrabec) Date: Fri, 16 May 2008 16:55:25 +0200 Subject: [phpLogCon] install.php remove or not In-Reply-To: References: <200805141625.01176.pvrabec@redhat.com> <200805161623.21874.pvrabec@redhat.com> Message-ID: <200805161655.25421.pvrabec@redhat.com> On Friday 16 May 2008 04:44:59 pm Andre Lorbach wrote: > > On Friday 16 May 2008 03:55:45 pm Rainer Gerhards wrote: > > > If I understood the bugzilla entry correctly, the empty file causes > > > other grief ;) > > > > > > So it might be good to add a comment to it (e.g. > > /*NOTCONFIGURED*/\n). > > > > Then, you could check that comment. Two problems solved ;) > > > > I agree /*NOTCONFIGURED*/\n is good idea. > > > > > Rainer > > > > > > On Fri, 2008-05-16 at 15:53 +0200, Andre Lorbach wrote: > > > > Hi, > > > > > > > > we could handle the configured / installed state different if we > > find no > > > > > other way around this problem. But if possible I would like to > > find an > > > > > alternative solution for the problem first. > > > > > > > > The installation method in phpLogCon is similar to the method used > > in > > > > > phpbb. > > > > Let me see. I can't find phpBB. :( > > > > > > There is another thing that clearly tells you if phpLogCon was > > already > > > > > configured, if the config.php file isn't empty anymore. By default > > an > > > > > empty one with write access is shipped, right? This config.php > > file is > > > > > written by the installation routine at the very end. So only if > > the > > > > > config.php file is empty, the update needs to copy the install.php > > file. > > > > > Is it possible to handle this by the package manager? > > > > I'm afraid it's not possible. I can only remove the file if it was an > > update. > > > But then there is rpm -V problem. > > Ok what I can do is, I can add a check like I described above. If the > config.php is empty, this means install.php is allowed to run. If the > size of config.php is more then 0, the install.php script will deny any > attempt to open it. In order to reconfigure phpLogCon, the config.php > file would need to be deleted or replaced with an empty one. thnx. Andre, I think this will push us further. I'm sorry I thought I can handle it in spec file, but I was wrong. I hope it helps other distros too. > Best regards, > Andre Lorbach > _______________________________________________ > phpLogCon mailing list > http://lists.adiscon.net/mailman/listinfo/phplogcon From alorbach at ro1.adiscon.com Fri May 16 16:57:10 2008 From: alorbach at ro1.adiscon.com (Andre Lorbach) Date: Fri, 16 May 2008 16:57:10 +0200 Subject: [phpLogCon] install.php remove or not In-Reply-To: <200805161655.25421.pvrabec@redhat.com> References: <200805141625.01176.pvrabec@redhat.com><200805161623.21874.pvrabec@redhat.com> <200805161655.25421.pvrabec@redhat.com> Message-ID: > I'm afraid it's not possible. I can only remove the file if it was an > > > > update. > > > > > But then there is rpm -V problem. > > > > Ok what I can do is, I can add a check like I described above. If the > > config.php is empty, this means install.php is allowed to run. If the > > size of config.php is more then 0, the install.php script will deny any > > attempt to open it. In order to reconfigure phpLogCon, the config.php > > file would need to be deleted or replaced with an empty one. > > thnx. Andre, I think this will push us further. I'm sorry I thought I can > handle it in spec file, but I was wrong. I hope it helps other distros too. No problem ;) - the more I think about this, the more I like this way to handle the install.php. -- Best regards, Andre Lorbach From alorbach at ro1.adiscon.com Mon May 19 15:40:07 2008 From: alorbach at ro1.adiscon.com (Andre Lorbach) Date: Mon, 19 May 2008 15:40:07 +0200 Subject: [phpLogCon] install.php remove or not In-Reply-To: <200805161655.25421.pvrabec@redhat.com> References: <200805141625.01176.pvrabec@redhat.com><200805161623.21874.pvrabec@redhat.com> <200805161655.25421.pvrabec@redhat.com> Message-ID: Hi again ;)! I want to inform you that I have made the changes in the current beta branch today. >From the changelog: Changed install.php handling, so it is not necessary to remove the script anymore. To avoid problems with automatic package updating, we changed the installer handling. From now, the install.php will be allowed to run only in two cases, first if the config.php file is missing, and second if the config.php file is empty. Download available from here: http://www.phplogcon.org/downloads The devel branch will be updated tomorrow. -- Best regards, Andre Lorbach > > update. > > > > > But then there is rpm -V problem. > > > > Ok what I can do is, I can add a check like I described above. If the > > config.php is empty, this means install.php is allowed to run. If the > > size of config.php is more then 0, the install.php script will deny any > > attempt to open it. In order to reconfigure phpLogCon, the config.php > > file would need to be deleted or replaced with an empty one. > > thnx. Andre, I think this will push us further. I'm sorry I thought I can > handle it in spec file, but I was wrong. I hope it helps other distros too. From alorbach at ro1.adiscon.com Tue May 20 16:59:17 2008 From: alorbach at ro1.adiscon.com (Andre Lorbach) Date: Tue, 20 May 2008 16:59:17 +0200 Subject: [phpLogCon] install.php remove or not In-Reply-To: References: <200805141625.01176.pvrabec@redhat.com><200805161623.21874.pvrabec@redhat.com><200805161655.25421.pvrabec@redhat.com> Message-ID: Hi again #2 ^^, as promised yesterday, here is the new Version from the devel branch v2.3.2, available from here: http://www.phplogcon.org/Downloads-req-viewdownloaddetails-lid-15.phtml The new version contains the install handling change from yesterday. Best regards, Andre Lorbach > -----Original Message----- > From: phplogcon-bounces at lists.adiscon.com [mailto:phplogcon- > bounces at lists.adiscon.com] On Behalf Of Andre Lorbach > Sent: Monday, May 19, 2008 3:40 PM > To: phplogcon at lists.adiscon.com > Subject: Re: [phpLogCon] install.php remove or not > > Hi again ;)! > > I want to inform you that I have made the changes in the current beta > branch today. > >From the changelog: > > Changed install.php handling, so it is not necessary to remove > the script anymore. > > To avoid problems with automatic package updating, we changed > the installer handling. > From now, the install.php will be allowed to run only in two > cases, first if the > config.php file is missing, and second if the config.php file is > empty. > > Download available from here: > http://www.phplogcon.org/downloads > > The devel branch will be updated tomorrow. > > -- > Best regards, > Andre Lorbach > > > > update. > > > > > > > But then there is rpm -V problem. > > > > > > Ok what I can do is, I can add a check like I described above. If > the > > > config.php is empty, this means install.php is allowed to run. If > the > > > size of config.php is more then 0, the install.php script will deny > any > > > attempt to open it. In order to reconfigure phpLogCon, the > config.php > > > file would need to be deleted or replaced with an empty one. > > > > thnx. Andre, I think this will push us further. I'm sorry I thought I > can > > handle it in spec file, but I was wrong. I hope it helps other distros > too. > > _______________________________________________ > phpLogCon mailing list > http://lists.adiscon.net/mailman/listinfo/phplogcon From pvrabec at redhat.com Tue May 27 10:58:44 2008 From: pvrabec at redhat.com (Peter Vrabec) Date: Tue, 27 May 2008 10:58:44 +0200 Subject: [phpLogCon] good news everyone :) Message-ID: <200805271058.44324.pvrabec@redhat.com> phplogcon passed the review finally. It was built in F9 and rawhide(F10), so I hope it will be available in fedora repositories soon. From alorbach at ro1.adiscon.com Tue May 27 11:01:19 2008 From: alorbach at ro1.adiscon.com (Andre Lorbach) Date: Tue, 27 May 2008 11:01:19 +0200 Subject: [phpLogCon] good news everyone :) In-Reply-To: <200805271058.44324.pvrabec@redhat.com> References: <200805271058.44324.pvrabec@redhat.com> Message-ID: Awesome news :) Great to hear that . Best regards, Andre Lorbach > -----Original Message----- > From: phplogcon-bounces at lists.adiscon.com [mailto:phplogcon- > bounces at lists.adiscon.com] On Behalf Of Peter Vrabec > Sent: Tuesday, May 27, 2008 10:59 AM > To: phplogcon at lists.adiscon.com > Subject: [phpLogCon] good news everyone :) > > phplogcon passed the review finally. It was built in F9 and rawhide(F10), so I > hope it will be available in fedora repositories soon. > _______________________________________________ > phpLogCon mailing list > http://lists.adiscon.net/mailman/listinfo/phplogcon