Re: [PHP] cgi bug workaround

2001-10-05 Thread Devon Weller


If you are getting #!/usr/local/bin/php output to the screen, then the
cgi scripts do no need the line in them to execute properly.  Do you have
access to the scripts?  Try removing this line altogether.  What happens?

- Devon

In article
[EMAIL PROTECTED],
[EMAIL PROTECTED] (James Peter Gregory) wrote:

 On Fri, 5 Oct 2001, David Robley wrote:
 
  On Fri,  5 Oct 2001 15:15, James Peter Gregory wrote:
   hi all,
  
   I've been asked to do some work on some servers where php can only run
   as cgi. Unfortunately it seems that php has a bug which means that
  
 #!/usr/local/bin/php
  
   gets printed out at the top of each page if I do this.
  
   Are there any workarounds for this? Is it fixed in the cvs versions?
  
   thanks,
  
   James.
 
  You should only need the #! construct if you are running that file as a
  php script from the shell/cron/whatever. If you are only serving pages
  via a web server (eg using WN or somesush) you use the server method to
  define those scripts as to be parsed by php and you don't need the #!
 
 I understand that. Unfortunately I'm not the one administrating this
 computer so we're stuck with having to find a work around for the problem.
 That is, I can't change the apache config at all. They'll only let us use
 cgi.
 
 but thanks all the same.
 
 James.
 
 
  --
  David Robley  Techno-JoaT, Web Maintainer, Mail List Admin, etc
  CENTRE FOR INJURY STUDIES  Flinders University, SOUTH AUSTRALIA
 
 Would I ask you a rhetorical question?
 

-- 
PHP General Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]




[PHP] Re: Sockets on FreeBSD Mac OS X

2001-10-03 Thread Devon Weller


Thanks for your help.  Here is some more information:

I am running the process from the command line as root.  I also tried
several different ports, all with the same result.

I don't think you need any special permission to bind to a port above
1024. If so, I couldn't find anything out about it.

Any other ideas?

Thanks,
- Devon



In article 04c401c14bc4$6a1ddde0$c801a8c0@Lynchux100, [EMAIL PROTECTED]
(Richard Lynch) wrote:

 Wild Guess:
 
 Your OS is configured to not allow nobody to bind port 12345, and PHP is
 running within Apache as nobody...
 
 Check out what sort of limitations are put upon users binding ports...
 
 If I was a real Un*x guru, I'd even know what command tells you that... :-|
 
 --
 WARNING [EMAIL PROTECTED] address is an endangered species -- Use
 [EMAIL PROTECTED]
 Wanna help me out?  Like Music?  Buy a CD: http://l-i-e.com/artists.htm
 Volunteer a little time: http://chatmusic.com/volunteer.htm
 - Original Message -
 From: Devon Weller [EMAIL PROTECTED]
 Newsgroups: php.general
 To: [EMAIL PROTECTED]
 Sent: Tuesday, October 02, 2001 11:02 AM
 Subject: Sockets on FreeBSD Mac OS X
 
 
 
  Has anyone successfully gotten socket functions to work with FreeBSD?
  More specifically, Mac OS X?
 
  I always get the following error: Can't bind to port 12345, exiting.
 
  The script works fine on Linux machines.  Is there a patch in the works
  for FreeBSD?  If so, I would be very happy.
 
  --
  Devon Weller
  [EMAIL PROTECTED]

-- 
PHP General Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]




[PHP] Sockets on FreeBSD Mac OS X

2001-10-02 Thread Devon Weller


Has anyone successfully gotten socket functions to work with FreeBSD? 
More specifically, Mac OS X?

I always get the following error: Can't bind to port 12345, exiting.

The script works fine on Linux machines.  Is there a patch in the works
for FreeBSD?  If so, I would be very happy.

--
Devon Weller
[EMAIL PROTECTED]

-- 
PHP General Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]