Hi, I have another question but maybe a new post would be too much for it - I'm having trouble registering a user/first admin to the new hub I have set up. I seem to have made all the needed files and changes and there are no error messages in the software log, but when connected to the hub doing +regme test or +test or even +help has no response at all. I tried copying the user.txt from the hub files on the Windows distribution I mentioned before, I had registered as per the First_Reg.cmd, with a oplevel of 10. Using that file in the linux- running hub has the client stuck after sending the password.
In case of not yet registered and no response in hub to +help etc after connection: AWAB entering IDENTIFY AWAB entering NORMAL TI56 entering IDENTIFY TI56 entering NORMAL WI4Q connected WI4Q ready WI4Q entering IDENTIFY WI4Q verifying IP 0.0.0.0 WI4Q verifying CID R3ZRC4U7H2LU3WASRXRJYY2PRHB7XDV6V3YFWQY WI4Q verifying nick TheLastGuardian WI4Q entering NORMAL When I use a users.txt file containing a registration for my nick, it has entering VERIFY at the end, stuck beyond that. I have checked settings.txt, min level to chat is 0, allowreg is 1, and so on. (same settings as the windows build, in which all works as expected. Any ideas where the issue might be? -- You received this bug notification because you are a member of Dcplusplus-team, which is subscribed to ADCH++. https://bugs.launchpad.net/bugs/1692364 Title: unable to compile recent adchpp builds on linux Status in ADCH++: Invalid Bug description: Hi. I've been trying to run a adchpp hub (migrating from ptokax). The provided Windows binaries for the latest version 2.12.1 works fine, but compiling the source for this newest version on linux fails. I've tried compiling on Ubuntu 14.04/16.04 x64 (inbuilt in windows 10 bash-on-windows), on Debian Jessie x64, and Raspbian Jessie on my raspberry pi 2B (arm). I referred to this question posted 3-4 years ago https://answers.launchpad.net/adchpp/+question/236015 which provided the info to remove the two lines in SConstruct to get the build compiling. However the binary generated does not run correctly: adchpp_2.12.1_source/build/debug-default-x64/bin] ./adchppd Starting. Core initialized .Thrown: FileException: Could not open file Unable to load adchpp.xml, using defaults: FileException: Could not open file . 2.12.1 (r"[unknown]") Debug running, press ctrl-c to exit... Logging: 2017-05-21 21:16:16: SocketManager: Starting Thrown: FileException: Could not open file LogManager::log: FileException: Could not open file Thrown: FileException: Could not open file LogManager::log2: FileException: Could not open file ^CLogging: 2017-05-21 21:16:20: core: Shutting down... Thrown: FileException: Could not open file LogManager::log: FileException: Could not open file Thrown: FileException: Could not open file LogManager::log2: FileException: Could not open file Shut downBusy pool objects: 0 I've pasted the scripts files and config files as required (in the same way as in the windows build of adchpp, where it works fine) I can paste the entire compile log if needed (it seems to compile fine, with # collect2 0.68 0.06 Move("build/debug-default/bin/socket/core.so", "build/debug-default/lua/LuaSocket/socket/core.so") scons: done building targets. at the end) ^This is from my rpi arm build, I've also tried x64 debug build and x64 release build options with the same apparent success in compilation. I also tried manually doing chmod 777 to all files in the build folder and running as sudo, still the same issues, seems to not be compiling properly. To manage notifications about this bug go to: https://bugs.launchpad.net/adchpp/+bug/1692364/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~linuxdcpp-team Post to : linuxdcpp-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~linuxdcpp-team More help : https://help.launchpad.net/ListHelp
