HipToday

I don't think I quite understand what you mean. But it sounds like you are confirming it should behave as before unless explicitly told different (i.e. don't change the default behavior). Maybe a proper layer-4 protocol would be nice, but I actually like the simplicity of the remote admin console. It's exactly what I want, it just took me forever to figure out how to actually login.

Really, the only thing missing from in-game commands (perhaps I just didn't see it) that I wanted to use RA for was account creation. That's how I ended up trying it out in the first place. Anyway, with or without backwards compatibility I don't think it'll take too much time/effort. I'll give it a shot and see if people want it. Thanks for the info. I suspected there would be other apps out there that relied on RA.

Is there a particular reason that when connecting to the Remote Admin Console that the user isn't prompted for their username and password? I'm looking into adding this functionality because I think a simple Username:/Password: prompt would be much more user-friendly than being greeted with the MOTD and then staring at a blinking cursor. It took me a fair amount of searching to find that to log in I needed to enter USER <USERNAME>, then PASS <PASSWORD>, then I'd finally be given the mangos> prompt. In that searching I came across this thread: Which talks about using the remote console for that application. I've already hacked together some code that works for me, but before I submit a patch I'd like to know if I need to maintain some backwards compatibility for applications such as the one above, or if there's just a very good reason that I'm unaware of as to why things are the way they are.

You could also alias that to 'mysql -p' then you'll be prompted for the password and you don't have to worry about it being in plain text in your startup scripts.

Your hint is right there. Getting MaNGOS going is no easy task, but the information is out there.

I have found that commenting out 'SUBDIRS += tbb' in ./dep/Makefile.am gets me past this build issue, but I'd appreciate confirmation that it is a sensible thing to do.

It seems that Intel's Threading Building Blocks isn't supported on OpenBSD, so I added -DUSE_STANDARD_MALLOC to AM_CPPFLAGS in ./src/framework/Makefile.ac. However, I'm still getting the following error: Am I going about this the wrong way? Is there a more complete way to disable TBB support?