This forum is a read-only archive of the Gammon Software forum (2000–2026). No new posts can be made. Search the archive.

Cygwin starting problems

Posted by Mopop on Tue 09 May 2006 03:08 AM — 12 posts, 42,865 views.

Mopop #0
This has never happened before but I wanna start up my mud and I keep getting this instead.

Limit: Command not found

This is all new to me and I tried messing with a few things, anyone know of the problem?
Zeno USA #1
Maybe it's not installed? Did you make sure the package is installed?
Mopop #2
Everything should be fine as I havent touched it for a month or 2. Why it is strange it stopped working here.
Zeno USA #3
What are you trying to do exactly? Run the startup script? Remember that it's case sensitive.
Mopop #4
./startup &

limit:Command not found
limit:Command not found

I really am starting to hate Cygwin -.-
David Haley USA #5
Did this work previously on the same computer, using Cygwin, or have you only just recently moved to Cygwin on this computer?
Mopop #6
It has always been on this computer :(
Conner USA #7
For those trying to help Mopop with this one, I'm on FC3 running SmaugFUSS 1.6-ish and my startup script also includes:

limit stacksize 1024k
limit coredumpsize unlimited

and it runs just fine, but if I type limit at the command line, I get: bash: limit: command not found

so I don't know that it's a matter of a missing package, but rather something reading the limit params in startup as if they were executable lines unto themselves.
David Haley USA #8
The startup script uses tcsh, if I remember correctly, so limit might be an internal tcsh command. That would explain why bash can't find it, but it wouldn't explain why it stopped working all of a sudden. Unless of course Mopop changed something and isn't telling us. :-)
Mopop #9
Er not that I know of!


#! /bin/csh -f

# Set the port number.
set port = 4000
if ( "$1" != "" ) set port="$1"

# Change to area directory.
cd ../area

# Set limits.
nohup
limit stacksize 1024k
limit coredumpsize unlimited
if ( -e shutdown.txt ) rm -f shutdown.txt

while ( 1 )
    # If you want to have logs in a different directory,
    #   change the 'set logfile' line to reflect the directory name.
    set index = 1000
    while ( 1 )
	set logfile = ../log/$index.log
	if ( ! -e $logfile ) break
	@ index++
    end

    # Record starting time
    date > $logfile
    date > ../area/boot.txt

    # Run SMAUG.
    # Check if already running
    set matches = `netstat -an | grep ":$port " | grep -c LISTEN`
    if ( $matches >= 1 ) then
        # Already running
        echo Port $port is already in use.
        exit 0
    endif
    ../src/smaug $port >&! $logfile

    # Restart, giving old connections a chance to die.
    if ( -e shutdown.txt ) then
	rm -f shutdown.txt
	exit 0
    endif
    sleep 5
end


Thats my startup script.
Colton #10
Eh, I get the same errors but mine just blows through them anyway. In truth since the limits arn't being set and there are no negitive affects for me just comment out the two limit lines:

#limit stacksize 1024k
#limit coredumpsize unlimited
Samson USA #11
Yeah, you can usually just ignore the limit errors. Since a core dump in Cygwin would actually be a Windows stackdump, they won't be of any help anyway. The rest of the script will run just fine without them.