[MrCallum]

When i do /samp03svr this comes up
samp03svr: amx/amx.c:799: expand: Assertion `memsize>=0' failed.
Aborted

[IDarkness]

Have you checked this?
http://support.sas.com/documentation...kyf59qgzvr.htm

[highstreetsrp]

try this.. might help you..
chmod 777 samp03svr
chmod 777 announce
than
nohup ./samp03svr &
this will help you to keep ur server online after closing putty

[linuxthefish]

Quote:

Originally Posted by highstreetsrp try this.. might help you.. chmod 777 samp03svr chmod 777 announce than nohup ./samp03svr & this will help you to keep ur server online after closing putty

Don't chmod stuff to 777 you idiot, +x is enough if you are just executing the file.

[Mark_Weston]

Quote:

Originally Posted by linuxthefish Don't chmod stuff to 777 you idiot, +x is enough if you are just executing the file.

*cough*says the scammer*cough*

777 in a non public directory won't make a huge difference.

[Sublime]

Quote:

Originally Posted by Mark_Weston *cough*says the scammer*cough* 777 in a non public directory won't make a huge difference.

It's not just about the directory, it's that any user/group can access and modify samp03svr to its will because it's chmod permissions are 777. Just to clarify, let me post the chmod permissions chart here :-



chmod 777 to a file gives any user, group or other visitors (the whole internet users, perhaps?) complete rights to do anything with the file as pleased, whereas chmod +x sets the file as executable only for [u]ser, [g]roup and [o]ther].

[linuxthefish]

Quote:

Originally Posted by Mark_Weston *cough*says the scammer*cough* 777 in a non public directory won't make a huge difference.

777 makes your files writable by others and executable by all (ugo+x), you could have a malicious user change the executable before it's next run...

How many fingers does your mother take?