On 01/15/2011 06:21 AM, Mesut GULNAZ wrote:
is it possible to see which php file(s) is/are sending emails on my server
by php.ini or with any other way?
coz i have a server and i have many domains and subdomains. on my smtp
systems i saw that many random mails are being sent from www server whic
On 01/15/2011 02:48 AM, Jesse Williams wrote:
I am attempting to compile php from source, because a couple of our developers
require a new version than what is packaged with our linux distribution (Oracle
Enterprise Linux 5.3). The code configures just fine and builds, but when I
run the 'mak
is it possible to see which php file(s) is/are sending emails on my server
by php.ini or with any other way?
coz i have a server and i have many domains and subdomains. on my smtp
systems i saw that many random mails are being sent from www server which
has RELAY permission. I know i must not give
On Thursday, January 13, 2011 12:45:30 pm Nathan Rixham wrote:
> David McGlone wrote:
> > Hi everyone,
> >
> > I think the subject is right, or somewhere close. Anyway I am trying to
> > perform a little trickery here with links. In the following code you can
> > see where I am trying to replace t
On 14 January 2011 18:48, Nicholas Kell wrote:
>
> On Jan 14, 2011, at 12:41 PM, Kai Renz wrote:
>
>> Hi guys and thanks for your answers...
>>
>> @Nicholas:
>> Yes, you are right. The first socket is only used if a new clients
>> connects, thats why the script generates a new port so the client c
I am attempting to compile php from source, because a couple of our developers
require a new version than what is packaged with our linux distribution (Oracle
Enterprise Linux 5.3). The code configures just fine and builds, but when I
run the 'make test' command it fails with something like thi
On Jan 14, 2011, at 12:41 PM, Kai Renz wrote:
> Hi guys and thanks for your answers...
>
> @Nicholas:
> Yes, you are right. The first socket is only used if a new clients
> connects, thats why the script generates a new port so the client can
> connect to the new socket. After that socket1 shoul
On Jan 14, 2011, at 12:41 PM, Kai Renz wrote:
> Hi guys and thanks for your answers...
>
> @Nicholas:
> Yes, you are right. The first socket is only used if a new clients
> connects, thats why the script generates a new port so the client can
> connect to the new socket. After that socket1 shoul
Hi guys and thanks for your answers...
@Nicholas:
Yes, you are right. The first socket is only used if a new clients
connects, thats why the script generates a new port so the client can
connect to the new socket. After that socket1 should continue its work
and wait for new clients.
@Daniel:
Yeh
On Fri, Jan 14, 2011 at 13:28, Kai Renz wrote:
(Putting this back on the list. Please use Reply-All.)
> @Daniel:
> Yeh i tried sending it to the background, this works but still it does
> wait for the other script to finish.
It shouldn't. In fact, just to see if I somehow completely f
Sorry, not sent to the list.
-- Forwarded message --
From: Evil Son
Date: Sat, Jan 15, 2011 at 4:26 AM
Subject: Re: [PHP] Exec Script in the background, don't wait till it finishes
To: Kai Renz
On Sat, Jan 15, 2011 at 2:56 AM, Kai Renz wrote:
> Hi there,
>
> i'm currently wor
On Fri, Jan 14, 2011 at 11:56, Kai Renz wrote:
>
> Now here is the problem:
> it all works fine, but the client can't send a quit message to socket1
> because socket1.php waits until socket2.php is finished. socket2.php
> is working properly, and if i connect to the new socket and quit the
> conne
On Jan 14, 2011, at 10:56 AM, Kai Renz wrote:
> Hi there,
>
> i'm currently working on a socket project. It consists of two scripts.
> The first script (socket1.php) creates a socket on a specified port
> and waits for a client to connect. If a client connects, they exchange
> some informations,
Hi there,
i'm currently working on a socket project. It consists of two scripts.
The first script (socket1.php) creates a socket on a specified port
and waits for a client to connect. If a client connects, they exchange
some informations, including a random created port. Next, the first
script cal
On Sat, Jan 15, 2011 at 2:19 AM, Richard Quadling wrote:
>
> error_reporting=-1
> display_errors=On
>
> will turn on everything and tell you about it.
Yes I see them now! Ghastly!
> Alternatively, take a look at the setting of php.ini-development. This
> is the recommended settings for developin
On 14 January 2011 16:06, Evil Son wrote:
> On Sat, Jan 15, 2011 at 1:51 AM, la...@garfieldtech.com
> wrote:
>> Assuming that by "bare strings" you mean:
>>
>> $foo[bar] = 'baz';
>>
>> as opposed to:
>>
>> $foo['bar'] = 'baz';
>
> Yes, indeed.
>
>> That is generally considered very bad form in PH
On Sat, Jan 15, 2011 at 1:51 AM, la...@garfieldtech.com
wrote:
> Assuming that by "bare strings" you mean:
>
> $foo[bar] = 'baz';
>
> as opposed to:
>
> $foo['bar'] = 'baz';
Yes, indeed.
> That is generally considered very bad form in PHP. That throws an E_NOTICE
> error level, and therefore sl
On 14 January 2011 15:51, la...@garfieldtech.com wrote:
> (I now expect to get flamed by someone who uses them but is insulted that I
> am calling them not respectable.)
http://www.alibaba.com/product-tp/103358451/FIRE_RETARDANT_SUIT_AND_COVERALL/showimage.html
I'd lend you mine.
If I had one.
Assuming that by "bare strings" you mean:
$foo[bar] = 'baz';
as opposed to:
$foo['bar'] = 'baz';
That is generally considered very bad form in PHP. That throws an
E_NOTICE error level, and therefore slows down your code (if only by a
small amount) for the error handling. Of course, if you
Hello group,
I am a new and just an occasional user of PHP and would like some direction.
I find the use of bare strings as array keys pleasant to work with,
easy on the eye and quick to type. I understand that this use of bare
strings is not encouraged because of possible conflicts with key word
20 matches
Mail list logo
