php-windows Digest 23 Jun 2003 07:02:02 -0000 Issue 1790

Topics (messages 20496 through 20506):

Re: Using PHP4
        20496 by: Stephen

Re: Subject: Parse error    what's this, what to do?
        20497 by: Dave Malen

Apache acts weird I think it's because of PHP
        20498 by: MoroSwitie

Re: where to find dll files
        20499 by: Melih Onvural

MOD L33T INFORMATION ONLY WORKS ON APACHE 1 NOT APACHE 2 ETC
        20500 by: Mark Clarkstone
        20501 by: Mark Clarkstone
        20502 by: Stephen
        20503 by: Mark Clarkstone

About Mod l33T READ THIS IF YOU WANT IT!
        20504 by: Mark Clarkstone

PEAR
        20505 by: Melih Onvural

Re: Fatal error: main(): Failed opening required..... Dreamweaver MX
        20506 by: Cristian MARIN

Administrivia:

To subscribe to the digest, e-mail:
        [EMAIL PROTECTED]

To unsubscribe from the digest, e-mail:
        [EMAIL PROTECTED]

To post to the list, e-mail:
        [EMAIL PROTECTED]


----------------------------------------------------------------------
--- Begin Message ---
Sorry, you will need to be a bit more detailed than that.

Where is this file?
How are you trying to open it?
What error message do you get?

Stephen

----- Original Message ----- 
From: "Mathias" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, June 22, 2003 3:53 PM
Subject: [PHP-WIN] Using PHP4


> Hello,
>     Now when I make a php file why can't I open it? Can anyone please
help?
>
>
> Mathias
>
>
>
> -- 
> PHP Windows Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>



--- End Message ---
--- Begin Message ---
Hi Neil

Thanks I needed that its been a long day lol

Cheers
Dave

"Neil Smith" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Dude - do you think we're telepathic or something ? How the hell are we
> supposed to know what you have written on line 129 ?!?!
>
> Neil.
>
> At 08:09 20/06/2003 +0000, you wrote:
> >Message-ID: <[EMAIL PROTECTED]>
> >Reply-To: "Ildiko Nyari" <[EMAIL PROTECTED]>
> >From: "Ildiko Nyari" <[EMAIL PROTECTED]>
> >To: <[EMAIL PROTECTED]>
> >Date: Thu, 19 Jun 2003 20:43:22 -0400
> >MIME-Version: 1.0
> >Content-Type: multipart/alternative;
> >         boundary="----=_NextPart_000_012F_01C336A3.6CA61A20"
> >Subject: Parse error    what's this, what to do?
> >
> >Hello
> >Parse error: parse error, unexpected '<' in C:\Program Files\Apache
> >Group\Apache2\htdocs\advanced3.php on line 129
> >
> >what's this?
> >I always get this error when I want to display the php files on the web,
> >so can't.
> >What do I do wrong?
> >
> >thanks,
> >ildiko
>



--- End Message ---
--- Begin Message ---
I have this strange problem,
I have apache version 2.0.46 installed and the latest version of php. (all
windows version)

sometimes the webservers doesn't respond anymore.
in your webbrowser you see that it has contacted the webserver, 
but all is extremely slow.

After a while everything is oke again, but on the server-status page
I see that,  under Parent server generations: the number has Increased bij
1

So if it says 5, I know that this problem has accured 5 times.

Does anybody know what could be the cause ?


--- End Message ---
--- Begin Message ---
Thanks for that response. I was being thick and not realizing that all of them had 
come with the zip file though i was told twice that this was the case. I looked back 
into my c:\PHP file and found everything there and then just opened them all in my 
php.ini file. thanks for the help and sorry for the ignorance.

melih


--- End Message ---
--- Begin Message ---
Links Don't work (Site Dead)


mod_l33t v1.0----

A fast, dynamic and limited virtual hosting module for Apache 1.3.x

This module has been tested on RedHat Linux 7.2 and Windows XP.

View the INSTALL file for instructions on how to install and configure
mod_l33t.

----------------

Why does this module exist?

Apache's virtual hosting is both slow and memory intensive.  On the server
at L33T.ca, with 6000 virtual hosts, each Apache thread used 64 MB of
memory, and it took apache about 20 seconds to start up.  *Each virtual host
took up about 10.5 kB of memory*. Reloading was just as hellish - if even
one virtual host was changed the server would have to be reloaded, taking up
to 20 seconds as well.  In addition, Apache often served pages slowly
(probably due to the fact that there were 40 of those Apache death-threads
running at any given moment).  Our server was dying horribly, crashing every
few days because of the ridiculous memory usage.

This module, while castrating the functionality of virtual hosts, makes
virtual hosting fast and memory efficient.  The server starts up instantly,
pages are served instantly, and *each virtual host now takes up about 0.3 kB
of memory*.  With 6000 virtual hosts each apache thread now uses 2.3 MB of
memory.

Our hosted users have noticed the massive stability and speed increase, and
are benefiting from it greatly.

If you need virtual hosting for just file redirection and user/group setting
for suexec, I suggest you give apache virtual hosting the ol' boot and try
out mod_l33t.  It's done wonders for L33T.ca.

----------------

Does this module really do virtual hosting?

It's better to think of this module as a file redirection layer that also
sets the User + Group for suexec, cuz that's all it really is at the moment.
mod_l33t perfectly suits the needs of L33T.ca web-hosting, so it could be
useful elsewhere.

In the future if there's a demand, this module could better replicate the
functionality of virtual hosting at a fraction of the memory cost and with
increased performance.

----------------

What makes this module so "dynamic"?

The module configuration file is read in every time it is modified.  So you
just edit the config file and the module will reload the configuration file
automatically.  No server restart/reload!  The configuration loads in just
milliseconds and is unnoticeable.

----------------

How is this module "limited virtual hosting"?

At L33T.ca we needed only the following directives for an effective virtual
host:

ServerName
User
Group
DocumentRoot
Alias

The User and Group directives are neccessary for running scripts securely
(suexec).  The ServerName, DocumentRoot, and Alias directives are neccessary
for pointing Apache to the right file.

---------------

Compatibility-wise, are virtual hosts in this module as good as a true
apache virtual host?

Hell no... for one thing, this module doesn't do real virtual hosting.  For
an example of poor compatibility, take cgiwrap: we found that mod_l33t
doesn't work with cgiwrap; however, in combination with suexec this module
has cgiwrap's functionality.  mod_l33t is largely untested, so its
compatibility with other modules is unknown.


---------------
---------------

Contact:

Post your bug reports, problems and questions in the L33T.ca support forums

http://forums.l33t.ca

---------------

Credits:

**L33T Kr3w**
- DethPigeon
- Mr.Oreo

http://www.L33T.ca




--- End Message ---
--- Begin Message ---
& if any one can make it work on apache 2 post here also


"Mark Clarkstone" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Links Don't work (Site Dead)
>
>
> mod_l33t v1.0----
>
> A fast, dynamic and limited virtual hosting module for Apache 1.3.x
>
> This module has been tested on RedHat Linux 7.2 and Windows XP.
>
> View the INSTALL file for instructions on how to install and configure
> mod_l33t.
>
> ----------------
>
> Why does this module exist?
>
> Apache's virtual hosting is both slow and memory intensive.  On the server
> at L33T.ca, with 6000 virtual hosts, each Apache thread used 64 MB of
> memory, and it took apache about 20 seconds to start up.  *Each virtual
host
> took up about 10.5 kB of memory*. Reloading was just as hellish - if even
> one virtual host was changed the server would have to be reloaded, taking
up
> to 20 seconds as well.  In addition, Apache often served pages slowly
> (probably due to the fact that there were 40 of those Apache death-threads
> running at any given moment).  Our server was dying horribly, crashing
every
> few days because of the ridiculous memory usage.
>
> This module, while castrating the functionality of virtual hosts, makes
> virtual hosting fast and memory efficient.  The server starts up
instantly,
> pages are served instantly, and *each virtual host now takes up about 0.3
kB
> of memory*.  With 6000 virtual hosts each apache thread now uses 2.3 MB of
> memory.
>
> Our hosted users have noticed the massive stability and speed increase,
and
> are benefiting from it greatly.
>
> If you need virtual hosting for just file redirection and user/group
setting
> for suexec, I suggest you give apache virtual hosting the ol' boot and try
> out mod_l33t.  It's done wonders for L33T.ca.
>
> ----------------
>
> Does this module really do virtual hosting?
>
> It's better to think of this module as a file redirection layer that also
> sets the User + Group for suexec, cuz that's all it really is at the
moment.
> mod_l33t perfectly suits the needs of L33T.ca web-hosting, so it could be
> useful elsewhere.
>
> In the future if there's a demand, this module could better replicate the
> functionality of virtual hosting at a fraction of the memory cost and with
> increased performance.
>
> ----------------
>
> What makes this module so "dynamic"?
>
> The module configuration file is read in every time it is modified.  So
you
> just edit the config file and the module will reload the configuration
file
> automatically.  No server restart/reload!  The configuration loads in just
> milliseconds and is unnoticeable.
>
> ----------------
>
> How is this module "limited virtual hosting"?
>
> At L33T.ca we needed only the following directives for an effective
virtual
> host:
>
> ServerName
> User
> Group
> DocumentRoot
> Alias
>
> The User and Group directives are neccessary for running scripts securely
> (suexec).  The ServerName, DocumentRoot, and Alias directives are
neccessary
> for pointing Apache to the right file.
>
> ---------------
>
> Compatibility-wise, are virtual hosts in this module as good as a true
> apache virtual host?
>
> Hell no... for one thing, this module doesn't do real virtual hosting.
For
> an example of poor compatibility, take cgiwrap: we found that mod_l33t
> doesn't work with cgiwrap; however, in combination with suexec this module
> has cgiwrap's functionality.  mod_l33t is largely untested, so its
> compatibility with other modules is unknown.
>
>
> ---------------
> ---------------
>
> Contact:
>
> Post your bug reports, problems and questions in the L33T.ca support
forums
>
> http://forums.l33t.ca
>
> ---------------
>
> Credits:
>
> **L33T Kr3w**
> - DethPigeon
> - Mr.Oreo
>
> http://www.L33T.ca
>
>
>



--- End Message ---
--- Begin Message ---
This a PHP helplist. We deal with php issues. Your issue is a Apache/Mod
l33t issue. I suggest looking somewhere else for support

Stephen

----- Original Message ----- 
From: "Mark Clarkstone" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, June 22, 2003 8:59 PM
Subject: [PHP-WIN] MOD L33T INFORMATION ONLY WORKS ON APACHE 1 NOT APACHE 2
ETC


> Links Don't work (Site Dead)
>
>
> mod_l33t v1.0----
>
> A fast, dynamic and limited virtual hosting module for Apache 1.3.x
>
> This module has been tested on RedHat Linux 7.2 and Windows XP.
>
> View the INSTALL file for instructions on how to install and configure
> mod_l33t.
>
> ----------------
>
> Why does this module exist?
>
> Apache's virtual hosting is both slow and memory intensive.  On the server
> at L33T.ca, with 6000 virtual hosts, each Apache thread used 64 MB of
> memory, and it took apache about 20 seconds to start up.  *Each virtual
host
> took up about 10.5 kB of memory*. Reloading was just as hellish - if even
> one virtual host was changed the server would have to be reloaded, taking
up
> to 20 seconds as well.  In addition, Apache often served pages slowly
> (probably due to the fact that there were 40 of those Apache death-threads
> running at any given moment).  Our server was dying horribly, crashing
every
> few days because of the ridiculous memory usage.
>
> This module, while castrating the functionality of virtual hosts, makes
> virtual hosting fast and memory efficient.  The server starts up
instantly,
> pages are served instantly, and *each virtual host now takes up about 0.3
kB
> of memory*.  With 6000 virtual hosts each apache thread now uses 2.3 MB of
> memory.
>
> Our hosted users have noticed the massive stability and speed increase,
and
> are benefiting from it greatly.
>
> If you need virtual hosting for just file redirection and user/group
setting
> for suexec, I suggest you give apache virtual hosting the ol' boot and try
> out mod_l33t.  It's done wonders for L33T.ca.
>
> ----------------
>
> Does this module really do virtual hosting?
>
> It's better to think of this module as a file redirection layer that also
> sets the User + Group for suexec, cuz that's all it really is at the
moment.
> mod_l33t perfectly suits the needs of L33T.ca web-hosting, so it could be
> useful elsewhere.
>
> In the future if there's a demand, this module could better replicate the
> functionality of virtual hosting at a fraction of the memory cost and with
> increased performance.
>
> ----------------
>
> What makes this module so "dynamic"?
>
> The module configuration file is read in every time it is modified.  So
you
> just edit the config file and the module will reload the configuration
file
> automatically.  No server restart/reload!  The configuration loads in just
> milliseconds and is unnoticeable.
>
> ----------------
>
> How is this module "limited virtual hosting"?
>
> At L33T.ca we needed only the following directives for an effective
virtual
> host:
>
> ServerName
> User
> Group
> DocumentRoot
> Alias
>
> The User and Group directives are neccessary for running scripts securely
> (suexec).  The ServerName, DocumentRoot, and Alias directives are
neccessary
> for pointing Apache to the right file.
>
> ---------------
>
> Compatibility-wise, are virtual hosts in this module as good as a true
> apache virtual host?
>
> Hell no... for one thing, this module doesn't do real virtual hosting.
For
> an example of poor compatibility, take cgiwrap: we found that mod_l33t
> doesn't work with cgiwrap; however, in combination with suexec this module
> has cgiwrap's functionality.  mod_l33t is largely untested, so its
> compatibility with other modules is unknown.
>
>
> ---------------
> ---------------
>
> Contact:
>
> Post your bug reports, problems and questions in the L33T.ca support
forums
>
> http://forums.l33t.ca
>
> ---------------
>
> Credits:
>
> **L33T Kr3w**
> - DethPigeon
> - Mr.Oreo
>
> http://www.L33T.ca
>
>
>
>
> -- 
> PHP Windows Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>



--- End Message ---
--- Begin Message ---
HUH ? this is about Apache & PHP


"Stephen" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> This a PHP helplist. We deal with php issues. Your issue is a Apache/Mod
> l33t issue. I suggest looking somewhere else for support
>
> Stephen
>
> ----- Original Message -----
> From: "Mark Clarkstone" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Sunday, June 22, 2003 8:59 PM
> Subject: [PHP-WIN] MOD L33T INFORMATION ONLY WORKS ON APACHE 1 NOT APACHE
2
> ETC
>
>
> > Links Don't work (Site Dead)
> >
> >
> > mod_l33t v1.0----
> >
> > A fast, dynamic and limited virtual hosting module for Apache 1.3.x
> >
> > This module has been tested on RedHat Linux 7.2 and Windows XP.
> >
> > View the INSTALL file for instructions on how to install and configure
> > mod_l33t.
> >
> > ----------------
> >
> > Why does this module exist?
> >
> > Apache's virtual hosting is both slow and memory intensive.  On the
server
> > at L33T.ca, with 6000 virtual hosts, each Apache thread used 64 MB of
> > memory, and it took apache about 20 seconds to start up.  *Each virtual
> host
> > took up about 10.5 kB of memory*. Reloading was just as hellish - if
even
> > one virtual host was changed the server would have to be reloaded,
taking
> up
> > to 20 seconds as well.  In addition, Apache often served pages slowly
> > (probably due to the fact that there were 40 of those Apache
death-threads
> > running at any given moment).  Our server was dying horribly, crashing
> every
> > few days because of the ridiculous memory usage.
> >
> > This module, while castrating the functionality of virtual hosts, makes
> > virtual hosting fast and memory efficient.  The server starts up
> instantly,
> > pages are served instantly, and *each virtual host now takes up about
0.3
> kB
> > of memory*.  With 6000 virtual hosts each apache thread now uses 2.3 MB
of
> > memory.
> >
> > Our hosted users have noticed the massive stability and speed increase,
> and
> > are benefiting from it greatly.
> >
> > If you need virtual hosting for just file redirection and user/group
> setting
> > for suexec, I suggest you give apache virtual hosting the ol' boot and
try
> > out mod_l33t.  It's done wonders for L33T.ca.
> >
> > ----------------
> >
> > Does this module really do virtual hosting?
> >
> > It's better to think of this module as a file redirection layer that
also
> > sets the User + Group for suexec, cuz that's all it really is at the
> moment.
> > mod_l33t perfectly suits the needs of L33T.ca web-hosting, so it could
be
> > useful elsewhere.
> >
> > In the future if there's a demand, this module could better replicate
the
> > functionality of virtual hosting at a fraction of the memory cost and
with
> > increased performance.
> >
> > ----------------
> >
> > What makes this module so "dynamic"?
> >
> > The module configuration file is read in every time it is modified.  So
> you
> > just edit the config file and the module will reload the configuration
> file
> > automatically.  No server restart/reload!  The configuration loads in
just
> > milliseconds and is unnoticeable.
> >
> > ----------------
> >
> > How is this module "limited virtual hosting"?
> >
> > At L33T.ca we needed only the following directives for an effective
> virtual
> > host:
> >
> > ServerName
> > User
> > Group
> > DocumentRoot
> > Alias
> >
> > The User and Group directives are neccessary for running scripts
securely
> > (suexec).  The ServerName, DocumentRoot, and Alias directives are
> neccessary
> > for pointing Apache to the right file.
> >
> > ---------------
> >
> > Compatibility-wise, are virtual hosts in this module as good as a true
> > apache virtual host?
> >
> > Hell no... for one thing, this module doesn't do real virtual hosting.
> For
> > an example of poor compatibility, take cgiwrap: we found that mod_l33t
> > doesn't work with cgiwrap; however, in combination with suexec this
module
> > has cgiwrap's functionality.  mod_l33t is largely untested, so its
> > compatibility with other modules is unknown.
> >
> >
> > ---------------
> > ---------------
> >
> > Contact:
> >
> > Post your bug reports, problems and questions in the L33T.ca support
> forums
> >
> > http://forums.l33t.ca
> >
> > ---------------
> >
> > Credits:
> >
> > **L33T Kr3w**
> > - DethPigeon
> > - Mr.Oreo
> >
> > http://www.L33T.ca
> >
> >
> >
> >
> > --
> > PHP Windows Mailing List (http://www.php.net/)
> > To unsubscribe, visit: http://www.php.net/unsub.php
> >
>
>



--- End Message ---
--- Begin Message ---
I have created a page online about mod_l33t
here & the download with Everything you need to install
http://homepage.ntlworld.com/albrecht/



--- End Message ---
--- Begin Message ---
Has anyone found a way to install PEAR components onto a Windows machine?

melih


--- End Message ---
--- Begin Message ---
One of two :
    - You don't have permission to open the Connection file.
    - The path to the Connection is wrong (maybe you have moved the file or
the directory else where).

It's less probably to be the read wrights because you are using the
Dreamweaver MX which put the files to the remote folder in the same way so
if you can see the advanced3.php in the browser you have to be able to see
also storeunclesam.php. I suppose is the second problem, you moved the files
in the Macromedia (or outside) and the paths are out of date. Re-open the
Recordset from the SB tab and choose OK and the Recordset will update it
self the path to the Connections. If this doesn't work then is really the
first problem.

-- 
-------------------------------------------------
Cristian MARIN - Developer
InterAKT Online (www.interakt.ro)
Tel:         +4021 312.53.12
Tel/Fax:  +4021 312.51.91
[EMAIL PROTECTED]
"Ildiko Nyari" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
What is this about? I can connect to mySQL database, but the website in
Explorer gives me this error.
What do I wrong? in Dreamweaver MX.
thanks

Warning: main(../../Connections/storeunclesam.php): failed to open stream:
No such file or directory in C:\Program Files\Apache
Group\Apache2\htdocs\advanced3.php on line 1

Fatal error: main(): Failed opening required
'../../Connections/storeunclesam.php' (include_path='.;c:\php4\pear') in
C:\Program Files\Apache Group\Apache2\htdocs\advanced3.php on line 1



--- End Message ---

Reply via email to