[DiscordArchive] Are you starting the process from a different folder than the one where authserver.exe is in?
[DiscordArchive] Are you starting the process from a different folder than the one where authserver.exe is in?
Original source
I'm not sure if it's specific to AzerothCore or not.
rektbyfaith
10-19-2023, 07:08 PM #21Archived author: Revision • Posted: 2023-10-19T19:08:21.188000+00:00
Original source
I'm not sure if it's specific to AzerothCore or not.
Original source
I have restarted mysql database, also the whole server, so far so good nothing happened with the console
rektbyfaith
10-19-2023, 07:14 PM #22Archived author: Charles Collins • Posted: 2023-10-19T19:14:24.325000+00:00
Original source
I have restarted mysql database, also the whole server, so far so good nothing happened with the console
Original source
<@234784691608092682>Dude, are you still online? I discovered an interesting phenomenon through testing
I wrote the daemon through Golang's exec.cmd and ran it on the Win11 system
The phenomenon is as follows:
When I set the absolute path to the top and run it directly, I will be prompted that configs/*. conf cannot be found
But when I execute authserver.exe again after entering the path, it does run normally
My uncertain summary:
1. Related to Windows, it is necessary to truly enter the current directory to truly run the current program, which may also reflect the execution logic of golang exec.cmd
rektbyfaith
10-19-2023, 07:57 PM #23Archived author: mateo • Posted: 2023-10-19T19:57:01.057000+00:00
Original source
<@234784691608092682>Dude, are you still online? I discovered an interesting phenomenon through testing
I wrote the daemon through Golang's exec.cmd and ran it on the Win11 system
The phenomenon is as follows:
When I set the absolute path to the top and run it directly, I will be prompted that configs/*. conf cannot be found
But when I execute authserver.exe again after entering the path, it does run normally
My uncertain summary:
1. Related to Windows, it is necessary to truly enter the current directory to truly run the current program, which may also reflect the execution logic of golang exec.cmd
Original source
2. It is related to Golang's exec.cmd. It does not directly call the exe program in the absolute directory, but through other methods (I have not yet looked at the source code)
rektbyfaith
10-19-2023, 07:57 PM #24Archived author: mateo • Posted: 2023-10-19T19:57:13+00:00
Original source
2. It is related to Golang's exec.cmd. It does not directly call the exe program in the absolute directory, but through other methods (I have not yet looked at the source code)
Original source
This is my code
You can now execute exe normally, but you must enter the current working directory
![[Image: image.png?ex=690c552d&is=690b03ad&hm=b02...badc7b8f8&]](https://cdn.discordapp.com/attachments/284406375495368704/1164653854495866990/image.png?ex=690c552d&is=690b03ad&hm=b02b56e0a3d88163934bef18f7a5152673424516a7df0a61de0f5ebbadc7b8f8&)
![[Image: image.png?ex=690c552d&is=690b03ad&hm=922...e329ac753&]](https://cdn.discordapp.com/attachments/284406375495368704/1164653854793683004/image.png?ex=690c552d&is=690b03ad&hm=9222fd7ba409d88836b1aeb3f2380c86c0f525d924057d5b6749422e329ac753&)
rektbyfaith
10-19-2023, 07:58 PM #25Archived author: mateo • Posted: 2023-10-19T19:58:37.260000+00:00
Original source
This is my code
You can now execute exe normally, but you must enter the current working directory
1 Guest(s)
1 Guest(s)