Login
User Name:

Password:



Register
Forgot your password?
Vote for Us!
tintin++ ogg sound player script for linux
Author: Robert Smith
Submitted by: Vladaar
6Dragons ogg Soundpack
Author: Vladaar
Submitted by: Vladaar
6Dragons 4.4
Author: Vladaar
Submitted by: Vladaar
LoP 1.46
Author: Remcon
Submitted by: Remcon
LOP 1.45
Author: Remcon
Submitted by: Remcon
Users Online
CommonCrawl, DotBot, Yandex

Members: 0
Guests: 14
Stats
Files
Topics
Posts
Members
Newest Member
481
3,739
19,386
621
KellieBusb
Today's Birthdays
Rane (42)
Related Links
» SmaugMuds.org » General » Smaug Snippets » Problems with shell code.
Forum Rules | Mark all | Recent Posts

Problems with shell code.
< Newer Topic :: Older Topic >

Pages:<< prev 1 next >>
Post is unread #1 Jan 15, 2003, 10:28 pm
Go to the top of the page
Go to the bottom of the page

Pharas

GroupMembers
Posts27
JoinedMay 22, 2002

I found 2 problems when trying to compile the shell code.
1) BUILDPORT and CODEPORT are both undeclared.
2) And this one, structure has no member named TESTINGMODE
       
Post is unread #2 Jan 21, 2003, 12:55 am
Go to the top of the page
Go to the bottom of the page

Samson
Black Hand
GroupAdministrators
Posts3,643
JoinedJan 1, 2002

Given that the readme clearly states no support will be given for that code, I'll leave it to you to figure out how to solve that.
       
Post is unread #3 Jan 24, 2003, 7:53 am
Go to the top of the page
Go to the bottom of the page

Pharas

GroupMembers
Posts27
JoinedMay 22, 2002

Had them taken care of before i posted. I was just letting you know in case you wanted to update your code. All that was needed was a couple of defines for codeport and buildport in mud.h, and to add testingmode to the system_data structure.
       
Post is unread #4 Jan 25, 2003, 7:13 pm
Go to the top of the page
Go to the bottom of the page

Samson
Black Hand
GroupAdministrators
Posts3,643
JoinedJan 1, 2002

Was all done on purpose actually. Makes it less likely someone can just slap it in and go. Which isn't what I want to see happening. You would agree that the code is inherently dangerous, yes? Not something an inexperienced admin should be playing around with.
       
Post is unread #5 Jan 27, 2003, 3:55 pm
Go to the top of the page
Go to the bottom of the page

Pharas

GroupMembers
Posts27
JoinedMay 22, 2002

You are correct.
       
Post is unread #6 May 27, 2003, 2:33 am
Go to the top of the page
Go to the bottom of the page

Somnio

GroupMembers
Posts39
JoinedMay 25, 2003

What he means is someone (me) cannot go "ooh! Shell!" then promptly rm -R /*
(then again, I can't even remember if that's the correct recursive option )
       
Post is unread #7 May 27, 2003, 11:16 am
Go to the top of the page
Go to the bottom of the page

Samson
Black Hand
GroupAdministrators
Posts3,643
JoinedJan 1, 2002

Heh, yes. That particular scenario is exactly what I'm after avoiding. Mainly because what inevitably happens is the person comes here and whines about how my code destroyed their mud. :P
       
Post is unread #8 Jul 21, 2003, 8:04 pm
Go to the top of the page
Go to the bottom of the page

Menion

GroupMembers
Posts10
JoinedJul 21, 2003

Do they ever whine about youre mud destroying their code? cackle like an idiot I just left what I was working on in the default afk directory... along comes my friend who want a seperate copy to experiment with so as to not mess anything up.. uses tar -zxvf afkmud* and wham heh (: so not only can youre code destroy a mud, youre mud can destroy my code! eheh
       
Pages:<< prev 1 next >>