[BlueOnyx:07097] Re: Perl not run on BO tarball onCentOS 5.5

Eiji Hamano bluequartz at hypersys.ne.jp
Tue Apr 19 04:38:23 -05 2011


> ----- Original Message ----- 
> From: "Eiji Hamano" <bluequartz at hypersys.ne.jp>
> To: "BlueOnyx General Mailing List" <blueonyx at blueonyx.it>
> Sent: Monday, April 18, 2011 8:44 PM
> Subject: [BlueOnyx:07091] Perl not run on BO tarball on CentOS 5.5
>
>
>> Dear
>> Is perl run  on BO tarball on CentOS 5.5 ?
>>
>> In my case, it never runs with error msg,
>>  "Supplementary GID of script userid less than configured minimum.".
>>
>> Any one advice me ?
>> Eiji Hamano
>> _______________________________________________
>>
>
> Eiji
>
> Make sure the script is owned by the admin user of that site; also make
> sure
> the group ownership is from that site.
>
> ----
> Ken M
> Precision Web Hosting, Inc.
> http://www.precisionweb.net


> From: "Eiji Hamano" <bluequartz at hypersys.ne.jp>
> To: "BlueOnyx General Mailing List" <blueonyx at mail.blueonyx.it>
> Sent: Tuesday, April 19, 2011 4:12 PM
> Subject: [BlueOnyx:07093] Re: [bluequartz] Re: Perl not run on BO tarball 
> onCentOS 5.5
>
> Yes  Ken.   I  already checkd  [BlueOnyx:04238] .
> And I checked the script 5 lines which was updated  for my test.
>
> I updated  it with sftp FileZilla. The ownership is  siteadmin : siteXX
>
> Eiji Hamano

Soory for my previos title.

I created a new site on the BO CentOS 5.5.
Then,  another perl error as follow;

## CGIWrap encountered an error while attempting to execute this script:
##
## Error Message: No such file or directory
## Error Number: 2
##
## This message usually indicates there is a problem with the script itself.
## Often this indicates either that the #! line of the script is incorrect,
## or the script was uploaded in binary mode instead of ascii mode.
##
## Check to make sure that the script does not have control-M's
## at the end of every line. That will prevent it from executing.
##
## An easy fix that takes care of this most of the time is to
## put '#!/.../perl --' instead of '#!/.../perl' on the first line of the 
script.
## This is typically a problem if the script was edited or uploaded
## from a DOS/Windows/Macintosh station to a unix based server

Then I modify the first line of the script from
"#!/usr/bin/perl"  to  "#!/usr/bin/perl --".

However  the oroginal site still "Supplementary GID" error.

Eiji Hamano









More information about the Blueonyx mailing list