secure_chroot_dir not persisting after reboot and stops VSFTPD server from starting #6
Description
Hello!
I have come across an issue with this formula where a reboot of the server causes VSFTPD to not start. This is due to the secure_chroot_dir /var/run/vsftpd/empty not persisting across reboots.
Default behaviour in CentOS/RHEL 7 is that this directory will be removed on restart of the server and not be created because neither the VSFTPD package or this formula creates a systemd tempfiles config.
The software should define what directories it needs in /run (which replaced /var/run in Fedora 15) by placing a configuration file in /usr/lib/tmpfiles.d. During the boot process, systemd-tmpfiles populates /run based on that configuration.
The default VSFTPD config from the package does not include the secure_chroot_dir setting.
So we can either remove this config setting or change the formula to deploy a systemd temfiles config. I'm willing to make a patch a pull request but want feedback on which way would be preferred. I'm only using this on CentOS 7 so I'd hope others could test it on other platforms like Ubuntu.
Thanks!