Waynn Lue wrote:
> Right, and I am, so I stayed away from that solution. My next
> attempt was to specify /usr/local/bin/php in the cron job, but that
> led to a problem because of the include paths. Now that I specific
> the full path, evidently the include path no longer is relative to the
> d
On Mon, Sep 29, 2008 at 9:34 AM, Richard Lynch <[EMAIL PROTECTED]> wrote:
> If you are running PHP as CGI, replacing the CGI with CLI could be
> problematic down the road...
>
> Right, and I am, so I stayed away from that solution. My next attempt was
to specify /usr/local/bin/php in the cron jo
On Mon, Sep 29, 2008 at 11:59 AM, Nathan Rixham <[EMAIL PROTECTED]> wrote:
> Shawn McKenzie wrote:
>>
>> Shawn McKenzie wrote:
>>>
>>> Waynn Lue wrote:
Yup, you're completely right. I checked the cronjob and got this:
PHP 5.2.6 (cgi) (built: Aug 11 2008 13:39:32)
Copyright
If you are running PHP as CGI, replacing the CGI with CLI could be problematic
down the road...
From: Waynn Lue [mailto:[EMAIL PROTECTED]
Sent: Sunday, September 28, 2008 6:12 AM
To: Richard Lynch
Cc: Per Jessen; php-general@lists.php.net
Subject: Re: [PHP] PHP + Cron jobs
Yup, you&#x
Shawn McKenzie wrote:
Shawn McKenzie wrote:
Waynn Lue wrote:
Yup, you're completely right. I checked the cronjob and got this:
PHP 5.2.6 (cgi) (built: Aug 11 2008 13:39:32)
Copyright (c) 1997-2008 The PHP Group
Zend Engine v2.2.0, Copyright (c) 1998-2008 Zend Technologies
with Advanced PHP
Waynn Lue wrote:
> Yup, you're completely right. I checked the cronjob and got this:
>
> PHP 5.2.6 (cgi) (built: Aug 11 2008 13:39:32)
> Copyright (c) 1997-2008 The PHP Group
> Zend Engine v2.2.0, Copyright (c) 1998-2008 Zend Technologies
>with Advanced PHP Debugger (APD) v0.9, , by George Sc
Shawn McKenzie wrote:
> Waynn Lue wrote:
>> Yup, you're completely right. I checked the cronjob and got this:
>>
>> PHP 5.2.6 (cgi) (built: Aug 11 2008 13:39:32)
>> Copyright (c) 1997-2008 The PHP Group
>> Zend Engine v2.2.0, Copyright (c) 1998-2008 Zend Technologies
>>with Advanced PHP Debugg
Yup, you're completely right. I checked the cronjob and got this:
PHP 5.2.6 (cgi) (built: Aug 11 2008 13:39:32)
Copyright (c) 1997-2008 The PHP Group
Zend Engine v2.2.0, Copyright (c) 1998-2008 Zend Technologies
with Advanced PHP Debugger (APD) v0.9, , by George Schlossnagle
Turns out there's
___
O/H Waynn Lue ??:
Perhaps this would do the job much better.
12 6 * * * php -f /home/foo/temp.php
Probably no different, unless the new-fangled -f implies -q, and he's running
the new version of PHP, which I doubt.
Also consider an alternative solutio
From: Waynn Lue [EMAIL PROTECTED]
Sent: Saturday, September 27, 2008 6:04 AM
To: Per Jessen
Cc: php-general@lists.php.net
Subject: Re: [PHP] PHP + Cron jobs
>
> > This is something that I've noticed for awhile, but last post to this
&g
You are using the old school PHP CGI as if it were PHP CLI.
Upgrade and use PHP CLI.
Or just add -q to the args:
12 6 * * * php -q /home/foo/temp.php
php -h
will show you the version and nature (CLI/CGI) of PHP you are running, as well
as the args and what they do, in rather terse format.
_
O/H Waynn Lue ??:
This is something that I've noticed for awhile, but last post to this
mailing list reminded me that someone probably already knows how to work
around this! I have a cron job that looks something like
12 6 * * * php /home/foo/temp.php
But even if temp.php doesn't output an
Waynn Lue wrote:
> Hm looks like it's CLI.
>
> $ php -v
> PHP 5.2.6 (cli) (built: Aug 11 2008 13:36:00)
> Copyright (c) 1997-2008 The PHP Group
> Zend Engine v2.2.0, Copyright (c) 1998-2008 Zend Technologies
> with Advanced PHP Debugger (APD) v0.9, , by George Schlossnagle
Yep, looks good -
Hm looks like it's CLI.
$ php -v
PHP 5.2.6 (cli) (built: Aug 11 2008 13:36:00)
Copyright (c) 1997-2008 The PHP Group
Zend Engine v2.2.0, Copyright (c) 1998-2008 Zend Technologies
with Advanced PHP Debugger (APD) v0.9, , by George Schlossnagle
Waynn Lue wrote:
> I actually am using MAILTO, and that's where the problem is. A
> cronjob only mails when there actually is output, which I'm fine with.
> In fact, when I run php temp.php from the command line, I don't get
> any output. But when it's part of the cronjob, there's that
> conten
>
> > This is something that I've noticed for awhile, but last post to this
> > mailing list reminded me that someone probably already knows how to
> > work
> > around this! I have a cron job that looks something like
> >
> > 12 6 * * * php /home/foo/temp.php
> >
> > But even if temp.php doesn't o
Waynn Lue wrote:
> This is something that I've noticed for awhile, but last post to this
> mailing list reminded me that someone probably already knows how to
> work
> around this! I have a cron job that looks something like
>
> 12 6 * * * php /home/foo/temp.php
>
> But even if temp.php doesn't
"James Mclean" <[EMAIL PROTECTED]> wrote...
> i do not have access to the cron system on my server, but
> would like to write a script that does some general housekeeping
> on my database, and various other things like removing old users,
> sending some newsletters etc...
What about putting the s
On Sat, 27 Jan 2001 18:05:08 +1030, "James Mclean"
<[EMAIL PROTECTED]> wrote:
>i do not have access to the cron system on my server
>The Sysadmin for the server is absolutly useless, so getting him to submit a
>cron job is no good.
>any ideas??
My idea:
We provide user cron access
The best way really is a cron job ... maybe you need a new ISP or a new
sysadmin.
Mick
> What would be the best way of getting the script to run on a timed basis,
> ideally the times and frequency of the script running defined in either the
> script its self, or another script.
> The Sy
20 matches
Mail list logo
