justdoug

Any help would be appreciated. Is that happening during the 'make install'? If so, it's a permission error. Use 'sudo make install' or make sure your destination directory has the proper ownership/permissions to be written to. A tip: if install is the problem and you do use sudo to force the issue, make sure to chown the files to the user running it (you). Running Mangos as root isn't all that safe.

Lock out everyone else except the owner (you) from the server/mangos executable and SQL. Level 4 is the account running Mangos (and/or having access to the SQL) and is the only one that has the Keys to the Promised Land.

freghar got it, and it's what I suspected. I was curious enough to ask those that know the codebase first rather than bang my head against the suspected wall. A quick overview of the server portion of the code looked like most of the prerequisites were already in place, with only detaching from the console and perhaps some signal handlers added to make it a true daemon. It looks to me like that's all that's required, but I'll now leave doing that to the people that know the code intimately when they decide things are ready. I'd just break things, I think. Thanks for the tips on shell scripts and screen. They're appreciated, but I'd already found them elsewhere in the forum (and discovered for myself that yes, running things NOHUP eats CPU like it's candy).

Just a little question about running Mangos as a true daemon on a *nix machine. After finally digging a little deeper around in the code, it looks to me that both realmd and mangosd could be convinced to run as well-behaved daemons. Leaving out the -DENABLE_CLI compile time flag would get it started, and some additions to detach from the console would do it- Or so it looks to me. In fact, it looks like things are pretty much set to go, with only that cli not being configured in and the pid and log files needing to be in place to make it so. Which brings me, finally, to my question: am I missing something and things +are+ ready to run as daemons and I'm merely thinking about reinventing the wheel, or does Mangos need serious tweaking to get along with init?

Comment? Sure! This thread deserves to be made sticky. It cleared up some things I was fuzzy on and answered some of the questions I had to solve for myself the hard way- which I'm sure would be of great aid to others following that same path.

Partly. The main Horde/Alliance factions are hard-coded (or so it seems from a cursory visit to the source code), while some sub-groups do seem to be allowed to be made friendly or at least less warlike. I've managed to get Friendly rep with the Stormwolf Clan, f'instance- much to the consternation of the local Drarves. If the faction comes up 'Neutral' when you first see it, you can toggle the 'At War' setting in the reputation panel of the client and go from there. However, this doesn't work for the main Alliance/Horde factions. The Defilers, Timbermaw Hold and others can also have their 'At War' setting turned off in the rep panel, but the others seem to be permanently set, hardcoded by the game code and keying on races.