You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Normally, if the tiny daemon doesn't have huge amount of Subnet = configuration, when run tincd -n network -kUSR2, the last entry will be:
May 16 21:42:37 hostname tincd: End of subnet list.
But I have one, which runs huge amount of Subnet =, where when issue tincd -n network -kUSR2, it appears it couldn't list all the entries, so the last line will be something like:
May 16 21:41:35 hostname tincd: 155.133.253.0/24#10 owner hostB
total entries in my case is around 900.
So my questions ares:
Are all the Subnet = announcements runs into the deamon, or only partial has been effectively runs in the daemon(since from tincd -n xxx -kUSR2 only shows partial of that)
Any limit or performance impact in terms of the huge amount of entries.
Normally, if the tiny daemon doesn't have huge amount of Subnet = configuration, when run tincd -n network -kUSR2, the last entry will be:
May 16 21:42:37 hostname tincd: End of subnet list.
But I have one, which runs huge amount of Subnet =, where when issue tincd -n network -kUSR2, it appears it couldn't list all the entries, so the last line will be something like:
May 16 21:41:35 hostname tincd: 155.133.253.0/24#10 owner hostB
total entries in my case is around 900.
So my questions ares:
Are all the Subnet = announcements runs into the deamon, or only partial has been effectively runs in the daemon(since from tincd -n xxx -kUSR2 only shows partial of that)
Any limit or performance impact in terms of the huge amount of entries.
@gsliepen
The text was updated successfully, but these errors were encountered: