Displaying 3 results from an estimated 3 matches for "setup_outgoing_connection".
2015 Jul 02
0
[PATCH 2/2] setup_outgoing_connection: log to LOG_DEBUG on if no known address
...l
discovered node already part of the network)
So log this to LOG_DEBUG
---
src/net_socket.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/net_socket.c b/src/net_socket.c
index 526d382..97d6c44 100644
--- a/src/net_socket.c
+++ b/src/net_socket.c
@@ -617,7 +617,7 @@ void setup_outgoing_connection(outgoing_t *outgoing) {
if(n)
outgoing->aip = outgoing->ai = get_known_addresses(n);
if(!outgoing->ai) {
- logger(DEBUG_ALWAYS, LOG_ERR, "No address known for %s", outgoing->name);
+ logger(DEBUG_ALWAYS, LOG_DEBUG, "No address known for %s", outgoing-&g...
2007 Feb 13
2
[PATCH] Eternal flush, memory leaks
...this:
logger(LOG_INFO, _("Flushing event queue"));
while(event_tree->head) {
event = event_tree->head->data;
event->handler(event->data);
event_del(event);
}
There's initially a setup_outgoing_connection() event there. It calls
do_outgoing_connection(), which on resolve failure calls
retry_outgoing(), which adds another setup_outgoing_connection()
event. Events are added as fast as they are taken away, and the flush
never terminates. And apparently connections are only removed in
build_fd...
2015 Jul 02
1
[PATCH 1/2] (read|append)_config_file: log open errors as LOG_DEBUG
In a "decentrally managed vpn" it is very likely that host config
files for some reachable nodes do not exist. Currently, tinc
fills the logs with "Cannot open config file" messages.
This commit changes the log level to LOG_DEBUG so
syslog doesn't get filled by default.
---
src/conf.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/conf.c