UnrealIRCd Forums

Hello,
I have installed TRE library in my server (debian sarge)
extracting TRE regex library
configuring TRE regex library
./configure: fork: Resource temporarily unavailable
configure: error: cannot run /bin/sh utils/config.sub
./configure: fork: Resource temporarily unavailable
compiling TRE regex library
make: *** No targets specified and no makefile found. Stop.
installing TRE regex library
make: *** No rule to make target `install'. Stop.
./configure: fork: Resource temporarily unavailable
configure: creating ./config.status
config.status: creating Makefile
./config.status: fork: Resource temporarily unavailable
config.status: creating src/modules/Makefile
./config.status: fork: Resource temporarily unavailable
config.status: creating unreal
./config.status: fork: Resource temporarily unavailable
config.status: creating ircdcron/ircdchk
./config.status: fork: Resource temporarily unavailable
config.status: creating include/setup.h
config.status: include/setup.h is unchanged

You hit some sort of limit of your box...
Maybe a reboot helps... (too many processes?)
maybe adding more RAM/Swap...
You could also check the output of ulimit -a

Generally this is a problem with shell accounts with anal limits configured. If you *are* on a shell, contact your provider and ask them if they can increase the process limit a bit (explain the situation) or, at worst, ask them if they can do the ./Config and make process.

w00t wrote:ask them if they can do the ./Config and make process.

Compiling as root is a really great way to stuff things up...

They could use su with the option to change login class (FreeBSD, something similar must exist for nix) to one that has no limits.

Or, they could change that user's pass if they didn't trust them, up the process limits, do what needed to be done, and reset everything

My way is less work... one command.

Blabla, if you cannot run ./Config on a shell, I wouldn't use it.
Must be fun every time you upgrade unreal...

That's a good point, but then, until recently I had such process limits on a shell (staffbox). I understood the reasoning behind it, but it got problematic when I couldn't even view a manpage :p so they got changed.