Dump through control socket

Note this removes SIGUSR1, SIGUSR2, and the graph dumping config option.
It seems cleaner to do everything through the control socket.
This commit is contained in:
Scott Lamb 2007-11-07 02:49:25 +00:00
parent 50ad3f2a89
commit 6eaefb4dbc
18 changed files with 113 additions and 125 deletions

View file

@ -885,16 +885,6 @@ Under Windows, use @var{Interface} instead of @var{Device}.
Note that you can only use one device per daemon.
See also @ref{Device files}.
@cindex GraphDumpFile
@item GraphDumpFile = <@var{filename}> [experimental]
If this option is present,
tinc will dump the current network graph to the file @var{filename}
every minute, unless there were no changes to the graph.
The file is in a format that can be read by graphviz tools.
If @var{filename} starts with a pipe symbol |,
then the rest of the filename is interpreted as a shell command
that is executed, the graph is then sent to stdin.
@cindex Hostnames
@item Hostnames = <yes|no> (no)
This option selects whether IP addresses (both real and on the VPN)
@ -1579,12 +1569,6 @@ New outgoing connections specified in @file{tinc.conf} will be made.
Temporarily increases debug level to 5.
Send this signal again to revert to the original level.
@item USR1
Dumps the connection list to syslog.
@item USR2
Dumps virtual network device statistics, all known nodes, edges and subnets to syslog.
@item WINCH
Purges all information remembered about unreachable nodes.