Either this feature is not working, or has unexpected behaviour.
Below I will put my launch parameters.
./arma3server -server -noSound -profiles=/home/arma/arma3/serverprofile/ -name=server -cfg=basic.cfg -config=server.cfg -ip=*...* -port=2302
The 'serverprofile' directory actually gets created by the serer, BUT, it does not create profile files or folders.
Naturally I attempted to create the files myself (using a copy of a file from my windows dedicated server) which didn't work.
I tried putting my server.arma3profile file in two different locations:
I also tried the root directory. So the bug is either that the profiles aren't read, aren't implemented, or has radically different behaviour than the windows version of the dedicated server.