* and then Matthew Sims declared
> > If a script is to be called with cron *outside* of the http directory,
> > how should file system paths be handled?
> >
> > Should I use
> >
> > fopen('a_path/relative_to/thescript.php');
> >
> > or
> >
> > fopen('/usr/var/www/absolute_file_path/thescript.p
> If a script is to be called with cron *outside* of the http directory,
> how should file system paths be handled?
>
> Should I use
>
> fopen('a_path/relative_to/thescript.php');
>
> or
>
> fopen('/usr/var/www/absolute_file_path/thescript.php');
>
> Im not only using this for fopen. So does php wo
* and then Nick Wilson declared
***bumpety bump*** ;-)
> If a script is to be called with cron *outside* of the http directory,
> how should file system paths be handled?
>
> Should I use
>
> fopen('a_path/relative_to/thescript.php');
>
> or
>
> fopen('/usr/var/www/absolute_file_path/the
* and then Greg Donald declared
> On Thu, 28 Oct 2004 18:27:34 +0200, Nick Wilson <[EMAIL PROTECTED]> wrote:
> > If a script is to be called with cron *outside* of the http directory,
> > how should file system paths be handled?
>
> I always assume cron is dumb and provide it with full paths.
On Thu, 28 Oct 2004 18:27:34 +0200, Nick Wilson <[EMAIL PROTECTED]> wrote:
> If a script is to be called with cron *outside* of the http directory,
> how should file system paths be handled?
I always assume cron is dumb and provide it with full paths.
--
Greg Donald
Zend Certified Engineer
http
5 matches
Mail list logo
