The policy rules for owampd are configured using the owampd.limits file; the details for configuring those policies are described in the owampd.limits(5) manual page.
The format of this file is:
The server can specify all the modes with which it is willing to communicate. The most strict mode that both the server and the client are willing to use will be selected.
This option should no longer be needed. If child processes are not exiting gracefully, please send a bug report to owamp-users@internet2.edu.
A liberal factor is recommended because this factor won't come in to play unless there are numerous duplicates, and that is precisely the kind of data most users will want to see. However, it is important to have this factor to ensure disk usage is not too vulnerable to replay DOS attacks of the test protocol.)
The valid values for diskfudge are 1.0-10.0.
This is important if the sender clock is running ahead of the receiver clock.
A session is complete timeout after the send time of the final packet. If the sender clock is ahead of the receivers clock, the sender will declare the session complete before the receiver. The receiver is only allowed to retain records for the packets that were sent at least timeout before it receives the stop sessions message from the sender. Therefore, if the sender clock is running ahead of the receiver clock, the receiver will be forced to delete some number of the final packets from the session.
This parameter directs the sender to wait enddelay after session completion allowing the receiver clock to be essentially enddelay later than the sender clock and still retain full sessions.
This option can be useful to limit log-file permissions to only users in this group.
Because the default port for owampd is in the protected range for most operating systems, it is usually required that owampd is stared as root. This option can be used to specify a non-standard port value that is not protected.
In the default case, owampd should be started as root so it can bind the default port 861. (See srcnode option.) owampd will release root permissions shortly after binding to this protected port and requests will be serviced by processes running with permissions defined by the user.