No Log.txt
Silent262
Join Date: 2012-09-21 Member: 160267Members
My server is either not generating a log.txt OR it is being generated out of my reach. The admin panel is not showing me the log in my root directory. I am in a non-default location, and being hosted by JestServers. I have already sent a ticket asking him, and I figured I would ask around here for ideas. I will get back to you when he responds, or if there are updates.
UPDATE:
Jest has responded and said that the logviewer is reporting all the txt files in the accessible section of the server. I do not have access, and, therefore, the log is either still being generated in appdata OR not at all. Any other thoughts, guys?
UPDATE:
Jest has responded and said that the logviewer is reporting all the txt files in the accessible section of the server. I do not have access, and, therefore, the log is either still being generated in appdata OR not at all. Any other thoughts, guys?
Comments
I am on a server. I do not have access to the AppData, and it is likely there is more than one NS2 server located on my box. I have NO access to AppData, and I cannot reasonably expect access to that location.
Let me be more blunt: I need a way to get a log without having access to AppData. I had a crash and would obviously like to report it. This will not happen, because I have no log. I need a commandline switch to move said log OR the log needs to be generated in the same directory as the Server.exe. If this is the case, then I am having a problem, and that deserves reporting, too.
I am not sure how your company has your server setup but I would image they are using the -file option in your command line, wherever the location leads is where the log.txt should be created.
They are most likely not specifying the log.txt file itself. If that is the case they would need to edit your command line to this;
-file "C:yourserver\log.txt"
-file "C:yourserver\log.txt"
I did just test it though and it does not break the server, server just ignores it since it doesn't see it as valid.
I don't think there is any way to change the log directory - I agree that this issue does need to be reported.