Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Ikh last won the day on December 24 2016

Ikh had the most liked content!

Community Reputation

14 Neutral

About Ikh

  • Rank


  • Gender

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Add intro UseItemEx a print who print prob change. Just to be sure.
  2. The difference is that you don't build these, but you also don't get to set options, and it's not guaranteed they will work with packages already on the system. That's why there are other commands like pkg upgrade. There are some special cases like using -march and -mtune .. Using march can cause problems , if you use march intro game core or db core and not using intro build ports can make a underfined behavior but that's not the case. The only reason to use ports inseated of package manager is build options. The packages is a prebuild port, and don't have flags like mtune and march.
  3. It really is not necessary for you to write so much. pkg install clang38 pkg install googletest pkg install cryptopp pkg install devil pkg install mariadb100-client pkg install gmake All in one.. pkg install clang38 googletest cryptopp devil mariadb101-client gmake I think the release version 3.8 of clang is enough
  4. Before killall After killall That does not mean the program is closed directly. As you can see game is not closed because he need to close all of his threads and all runing stuffs. Destroy arenaManager Destroy ItemManager Destroy CClientManager When u see in syslog this mean there is nothing shit when using KILLALL I try to explain you because you used " SHIT " word Thank you
  5. Really ? Do you know what a .killscript is ? killall sends a signal to all processes running any of the specified commands. If no signal name is specified, SIGTERM is sent. KILL ALL don't kill the process directly / send the SIGTERM void signal_setup(void) { signal_timer_enable(30); signal(SIGVTALRM, checkpointing); signal(SIGHUP, hupsig); signal(SIGCHLD, reap); signal(SIGINT, hupsig); signal(SIGTERM, hupsig); signal(SIGPIPE, SIG_IGN); signal(SIGALRM, SIG_IGN); signal(SIGUSR1, usrsig); } SIGTERM don't close you program imediatly. Just use killall game you
  6. There is nothing to be fixed. killall name_of_game name_of_db is already enough Just remove && reboot from Tasho .sh
  7. You also need to wait 5-10 seconds sometimes #!/bin/sh #[i] If processes change their name, killall may not be able to match them correctly, so change "game" or "db" with your name, type "ps" or "top" for know. echo -e "Kill processes and reboot server ..." killall game db && sleep 10 && reboot You can also move reboot.sh intro /usr/local/sbin and name it simply r in this way you not need always to cd /path/to_reboot.sh you can write simply r and enter .. etc
  8. Is this what you need ? http://stackoverflow.com/questions/13179410/check-whether-one-specific-process-is-running-on-windows-with-c You not need a loop for that. Just search on google
  9. The thread destructor will terminate your program if the object is destroyed while the thread is still running. Do you know what is a thread ? Is not better to create a class for TestFunc and after you call? Or you can even make function inline. while(1) in above example these statements will be executed forever... and will never stops. You are sure about that? You may use an "if condition" and inside it a break statement to terminate loop in some specific situation. I do not really understand what you want to do. inline void TestFunc() { std::ofstream ofs("example.t
  10. sys_err("Nullpointer in CHARACTER::GetQuestFlag %lu FLAG: %u", GetPlayerID(), flag); And you can see the flag who make this error
  11. locale.cfg change charset dear
  12. BUY SYSTEM FROM LENNT that's my advice
  13. This mean there's no character or is dead.
  • Create New...

Important Information

Terms of Use / Privacy Policy / Guidelines / We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.