Re: Bug in #! processing - "pear broken on current"

From: Roman Neuhauser (neuhauser_at_sigpipe.cz)
Date: 06/10/05

  • Next message: Dag-Erling Smørgrav: "Re: Bug in #! processing - "pear broken on current"" 
    Date: Fri, 10 Jun 2005 08:24:31 +0200
To: Garance A Drosehn <gad@FreeBSD.org>

    # gad@FreeBSD.org / 2005-06-09 12:37:20 -0400:
    > [moved over from the thread:
    > Re: cvs commit: src/sys/kern imgact_shell.c
    > on the cvs-src mailing list...]
    >
    > At 11:03 AM -0500 6/9/05, Matthew D. Fuller wrote:
    > >
    > >Well, I dunno what part of it is giving troubles (and I haven't seen
    > >it myself, since I'm still on RELENG_5 for the moment; just keeping my
    > >eyes open). It doesn't seem like a terribly esoteric line though:
    > >
    > >#!/usr/local/bin/php -n -q -dsafe_mode=0 -doutput_buffering=1
    >
    > It is very likely that the problem which is being seen with this
    > script is due to the change in parsing I committed on May 28th.
    > Before the change, php would have been started up with:
    >
    > [0] -> /usr/local/bin/php
    > [1] -> -n
    > [2] -> -q
    > [3] -> -dsafe_mode=0
    > [4] -> -doutput_buffering=1
    > [5] -> /usr/local/bin/name-of-script
    > [6...] -> parameters specified by user
    >
    > and now php is being started with:
    >
    > [0] -> /usr/local/bin/php
    > [1] -> -n -q -dsafe_mode=0 -doutput_buffering=1
    > [2] -> /usr/local/bin/name-of-script
    > [3...] -> parameters specified by user
    >
    > Assuming 'php' does not know what to do when all those options are
    > glommed together in a single argument, then the above script would
    > not work right on any other operating systems either. The change
    > I made on the 28th gets FreeBSD to work more like other OS's when
    > it comes to parsing that #!-line in scripts.

        The pear people have hacked around the other OS's limitations.

        This change makes FreeBSD lose one small but fine competitive
        advantage over other unix-like systems. Pity. 

    -- 
How many Vietnam vets does it take to screw in a light bulb?
You don't know, man.  You don't KNOW.
Cause you weren't THERE.             http://bash.org/?255991
_______________________________________________
freebsd-arch@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org"
  • Next message: Dag-Erling Smørgrav: "Re: Bug in #! processing - "pear broken on current""

    Relevant Pages

    • Re: Whats slowing things down?
      ... and Postgres 8.1 on Debian 4.0. ... when the parsing is finished; ... but there's only one instance of the PHP parser than can parse web ... That if one PHP script is bogging down on the server, ...
      (comp.lang.php)
    • Re: Bug in #! processing - "pear broken on current"
      ... >> script is due to the change in parsing I committed on May 28th. ... >> not work right on any other operating systems either. ... > This change makes FreeBSD lose one small but fine competitive ...
      (freebsd-arch)
    • Re: [PHP] PHP console script vs C/C++/C#
      ... My script is taking a longer time to execute than I want. ... I prefer to write in PHP because that is what I know best. ... This is why I am thinking about rewriting my whole script in a C language. ... Perhaps there are different methods I could be using to speed up execution. ...
      (php.general)
    • Re: How to Add a Feeback Form
      ... I saw nothing in that script that indicates where the form is e-mailed to so ... Greg Maxey/Word MVP ... PHP or not. ... have the support available yet. ...
      (microsoft.public.frontpage.programming)
    • How best to show PHP source? (was: One page, multiple submit buttons)
      ... script to add to the top of a PHP script to enable showing its ... Maybe anybody submitting their own PHP code for critique here ... Anything posted to a newsgroup is a "snapshot" of what the ... there ought to be a FAQ for this ...
      (comp.lang.php)