OpenEuphoria

Re: Linux, exu and the exit code 127

• Posted by Robert Craig <rds at RapidEuphoria.com> Oct 25, 2003
• 379 views

Carl W. wrote:
> Having just acquired a Mandrake Linux install to play with, I though 
> Euphoria would be a good addition, despite me not having much time for 
> it these days.
> 
> The install was painless and the config files (such as .bashrc) were 
> simple to edit.
> 
> So I ran exu. Nothing.
> 
> I ran ( exu ; echo $? ). Nothing but an exit code of 127.
> 
> Searching the mailing list archive I came across the problems chris, aka 
> tubby.toast was having back in February.
> 
> With root access to the box I have, and a little help from chris's 
> thread, here's a couple of requirements 'missing' from RDS's list for 
> exu to run under Linux:
> 
> The /proc 'directory' on the system *must* be at least read/executable 
> by all; i.e. permissions set to 555. Most systems have this set by 
> default, but some System Administrators lock it down to just 500 or 511 
> 'for security reasons'. This was how I found the system I inherited, and 
> the cause of my problems in the first place.
> 
> The /tmp directory should be globally read/write/execute - permissions 
> 777. Again - some Sysadmins lock this down.
> 
> An ISP, for instance, might be persuaded to make the above changes to 
> their servers if somebody's CGI doesn't run at all after uploading.

Thanks. I'll mention those requirements in the
installation docs, although I can't recall more than
maybe one or two people complaining about those things.

They are required because exu is compressed with UPX.
If you create a decompressed exu, those requirements
won't exist.

Regards,
    Rob Craig
    Rapid Deployment Software
    http://www.RapidEuphoria.com