Control socket interface.

In the future, username/password checking will be added for connections to the control socket. Command authorization, where the commands entered by the administrator are run through a virtual server before they are executed, will also be added in future.

For now, anyone who has permission to connect to the socket has nearly complete control over the server. Be warned!

This functionality is not enabled by default.

See also the "radmin" program, which is used to communicate with the server over the control socket.

listen {

	type = control
	socket = ${run_dir}/${name}.sock
#	uid = radius
#	gid = radius
#	mode = rw