If your system is using systemd's systemd-sysctl.service and not sysctl for the setting at boot time then things are a little different than sysctl.
systemd-sysctl sorts all of the configuration file names, ignoring the directory name, and then loads them in that order irrespective of the directory they were in. This means that if you put your setting in /...
I had exactly same question. In my case, chroot_local_user=YES didn't work well. If enable it, the below error message was returned when I tryed to login:
500 OOPS: vsftpd: refusing to run with writable root inside chroot()
To solve it, I added allow_writeable_chroot=YES. This config is not mentioned in man page, but it works well.
The version numbers mentioned in the question seem to suggest that you are referring to Centos 6.
Centos 6 is EOL since November 30th, 2020, so the backported fixes that you refer to are now purely theoretical.
It is however correct that, while still supported, the distribution was delivering security updates to their packaged version rather than new ...
Nothing of that will be "leaked".
The computer will try to connect to a server which is not there. A network sniffer will only see a TCP connection attempt; but since the connection never will get established, application-specific details such as requests for a specific SMB share or logon information will not be exchanged at all.
If you only do that for a small time in order to test the connection, it should be fine; but it's better to use a spare PC with nothing important on it.
BTW, that "ISP-provided Ethernet cable" is definitely connected to a router somewhere, otherwise it would have no connectivity at all.
A few problems I can think of
Duplicate collection names
Performance issue is there as you might not be able to control the indexes
A different approach would be you create the collection for them and let them put the data into a mixed field. Still you will face the indexing problem at some extend.