- tar -zxvf lundftpd*.tar.gz
- cd lundftpd/
It requires gnumake, which could be called "make", "gmake" or "gnumake" on your system.
If all goes well, you should have a "lundftpd" binary.
You can now copy the binary executable "./lundftpd/src/lundftpd" and example configuration file "lundftpd.conf" to a desired location, or test it where it is. Either is fine.
Edit your lundftpd.conf. But I would recommend only changing items as port and paths. Once it works, you can start to tweak. Most people will set the quota setting in lundftpd.conf to a negative value which will break everything.
The default "lundftpd.conf" assumes you use "ftp-data/" as a subdirectory from where you start lundftpd to store its data files. You will need to create it, and "ftp-logs".
- mkdir ftp-data
- mkdir ftp-logs
Create yourself of at least one login (presumably with admin privileges).
- ./lundftpd -a
You can give it privilege of "UF_ALL". Then you can do all other administrations with "SITE" commands.
=== Step 5 === Start lundftpd. The first time it can be handy to start it with logging on.
- ./lundftpd -v
This way you can spot any issues it might have on your system. Hit ^C to exit it, and to run it properly in the background, use:
Remember to start lundftpd in the directory where ftp-data/ is!
Login, and look around. Tweak your "lundftpd.conf" until you are happy. When lundftpd is running, you will notice it is three processes. (Unless you have increased the number of dirlist child helpers). To stop lundftpd, you can just send "INT" to the main one. (Generally the process with the lowest <pid>)
- kill -INT <pid>
- pkill -INT lundftpd
INT tells it to cleanly finish, let the checker child save its list of entries to test and exit. If you HUP it, or use -9, the checker child will just exit, and if there were files to test in the queue, they will not be tested. (Unless you use "SITE RESCAN" to re-issue those missed entries).