Share configuration

Listen port
For each directory that is shared by kpf, a new network 'port' is opened. A 'port' is simply a number used to uniquely identify a network service. When someone uses a program (e.g. a web browser) to connect to a machine, it is directed to the service by specifying the address of the machine and the 'port' on which the service is running.
The 'port' concept allows one machine to run more than one network service. Services you might use every day include HTTP (the web,) usually connected to by port 80, SMTP (mail sending,) usually on port 25, and POP3 (mail receiving,) usually on port 110.
Usually, when you connect to a network service, you do not need to specify which 'port' you want to connect to. This is because the ports are standardised, so anyone connecting to port 80 on a network machine expects to find an HTTP (web) server.
kpf is not a 'standard' service, so 8001 was chosen for the default port.
The second directory you share will offer to listen on port 8002, with the number being incremented each time you start a new share.
Within certain boundaries, you are free to choose whichever port number you wish, for a share.
It is usual for port numbers below 1000 to be reserved for 'system' services, i.e. those under the control of the machine's administrator, therefore you may find that attempting to use anything below 1000 will simply not work.
kpf tries to warn you when it cannot 'listen' on a port. It does this by displaying a 'broken connection' icon over the top-left corner of the graph. kpf attempts to stop you assigning more than one share to the same port, but it will not attempt to stop you setting a share to listen on a port which is already occupied by another service, for example your 'real' web server.
If you see the 'broken connection' icon, right-click on the bandwidth graph and choose 'Configure...' Now try changing the listen port and pressing 'Ok'. Assuming that this time you picked a free port, you should see that the 'broken connection' icon disappears, and you should now be able to connect to the share.

Bandwidth limit
The term 'bandwidth' refers to the amount of data that may be transmitted over a connection during a period of time. Techies may be overheard referring to how 'fat' their 'pipe' is. The analogy is apt.
kpf allows you to set a limit on how much bandwidth will be used by a particular share. This is useful when you want to avoid your network connection being saturated by people downloading from your shares. If you are on a modem, for example, you only have a few kilobytes per second to yourself. Limiting the bandwidth used by your kpf shares will allow you to keep a portion of the bandwidth for your own use.
As just mentioned, kpf measures bandwidth in kilobytes per second, or kB/s for short. A typical modem transfers about 5kB/s on average, so limiting the total use of all kpf shares to a value less than this may be wise, depending on how you are using kpf.

Follow symbolic links
A symbolic link is a special file which is a reference to another file (or directory) in your filesystem. By following the link, you reach the file or directory referred to - the link is generally transparent.
By default, a kpf share does not allow the following of symbolic links. This means that, for example, if you have a share pointing to /your/home/directory/public_html and you create a link inside public_html, pointing to /tmp, then anyone requesting /tmp will see the contents of your /tmp directory.
In general, it's a bad idea to allow the following of symbolic links in this way. The main reason this is allowed is so that you may have symbolic links inside the shared directory, which point to another place inside the shared directory. This can be useful if you're serving up an entire 'website' - which as mentioned previously, is not the intended use of kpf.
Just be careful not to link to anywhere on your filesystem that might hold sensitive information (or have a symbolic link in it somewhere that points to sensitive information!)