Server version: 184.108.40.206 6801
OS: Linux Dedicated
MM version: 1.10.961 (latest)
SM version: 1.8.6041 (latest)
Found this topic
from 8 years ago with the same issue with no solution. Think 8 years later you wouldn't experience anything like that.
I've recently rented 2 Linux servers from 2 different server hostings and both of them have this issue. The plugins work, create default CFGs on first launch, but modifying them has no effect whatsoever. You change cvars, save files, everything is alright, but the plugin still uses default values.
I have absolutely zero idea how to resolve this issue and thought maybe anyone running servers on Linux can shed some light on it. This is crucial for someone like me, who's planning to use a ton of plugins.
Everything worked fine on the old windows OS (different server, different hosting).
Thank you in advance.
UPD (Support response):
"The problem hasn't been mentioned by clients hosting any other source engine game, which would suggest that the problem is possibly only present in the L4D2 configuration file parser.
I would guess that the problem might be related to the different new line and/or end of file markers used in Linux. I've attached a list of the file content types of each of the .cfg files within your server's directory. This seems to indicate that the vast majority of them have CL RF (\r\n) line endings, which are normally used on Windows.
For further information, the Linux distribution our servers run is currently Ubuntu 14.04 x64."
The problem persists even after changing to Unix. But small .cfg files can actually be modified.
UPD3 (Support response):
"I've attached the full console log that is written when the server starts up, perhaps there's some useful information here.
We would certainly assume that the problem is related to "Cbuf_AddText: buffer overflow" which can be seen in the attached log file.
If the configuration options can be applied via the console/RCON after the server has started up, perhaps one roundabout solution would be to write a script which would automatically parse the .cfg files and execute each of the configuration items on RCON."
My talk with support ends here. They suggested to write a specific script. I don't want to deal with that and will look for other workarounds. For now it's recompiling the needed plugins in Spider and setting the default values in them to what I need.
I hope that one day this talk with myself will be useful for someone who finds themselves in the same situation. n_n)b